Clear Semantic Index

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already convey destructiveHint=true and idempotentHint=true, indicating deletion and safe re-execution. The description adds minimal context (removing 'corresponding ...') but is incomplete. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single incomplete sentence, which is concise but poorly structured. It fails to complete the thought, indicating rushed or truncated content. Front-loading is not effective due to the break.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and no output schema, the tool is simple, but the description is incomplete and lacks details about what exactly gets deleted (e.g., embeddings, metadata). For a destructive action, more completeness is expected, such as noting irreversibility or backup needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Baseline of 4 applies; description does not need to add param details. The incomplete description does not detract from parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Title 'Clear Semantic Index' and description 'Delete all indexed data from the local vector store' specify the action and resource. It distinguishes from sibling tools like semantic_index (create) and semantic_search (query). However, the description is incomplete (trailing '...'), slightly reducing clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like semantic_delete or spotlights. The description implies clearing all indexed data, but fails to mention prerequisites or consequences (e.g., irreversible data loss). No when-not information is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.