clear_index

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

The description discloses the side effect of cache removal and the consequence that subsequent calls rebuild/reload. With no annotations, this provides adequate transparency for a cache management tool, though it omits details like authorization or rate limits.

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?

Two sentences, no fluff. Every word earns its place, front-loading the core action and following with a consequence.

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?

The description covers the main action and effect but is slightly ambiguous about omitting both parameters. With no output schema and simple semantics, it meets a minimal viable level but could clarify the default source behavior.

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?

Both parameters are documented in the schema, and the description adds the advice 'Omit only when the server has a default source,' which clarifies the source parameter's usage. This adds value beyond the schema descriptions.

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?

The description clearly states the action: 'Remove the selected source from the in-memory MCP cache.' It uses a specific verb and resource, and the tool is easily distinguished from siblings like 'refresh_index' or 'search.'

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, such as refresh_index. The description only implies usage for cache invalidation but does not set conditions or exclusions.

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