Clear Search

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

Annotations already set idempotentHint=true, so the description's mention of 'frees memory' adds behavioral context. It correctly notes the operation removes a completed search, consistent with idempotent hint (removing a completed search is idempotent). 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 extremely concise: two sentences and an Args section that is minimal. No wasted words, and the key information is front-loaded.

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 the tool's simplicity (single param, no output schema, annotations clear), the description is complete enough. It does not explain return values, but that's acceptable when no output schema exists and the operation is straightforward.

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?

The input schema has 100% coverage and a clear description for search_id ('Search ID or "all"'). The description repeats this but clarifies 'all' means 'all completed', adding value by specifying the scope.

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 tool removes a completed search and frees memory, specifying the verb 'removes' and resource 'completed search'. It distinguishes from siblings like fc_stop_search (stops running search) and fc_start_search (starts 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?

The description implies usage when a search is completed, but does not explicitly state when not to use (e.g., for running searches) nor mention alternatives like fc_stop_search. However, context from sibling names provides differentiation.

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