create_search_recent_remove

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

Annotations already cover idempotency and destructive hint. The description adds that it's a POST operation and instructs to read the GET/schema for fields, but provides no side effects, return values, or additional behavioral context, contributing minimal value beyond 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?

Two concise sentences with no fluff. It front-loads the action and resource, includes the endpoint, and mentions the argument. Though minimal, it is efficiently structured.

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 tool has an output schema, but the description doesn't mention return values. The open-ended body is left completely unexplained, requiring external lookup. For a removal operation, it lacks sufficient context for correct invocation without additional resources.

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 sole parameter 'body' is an open-ended object with no schema description (0% coverage). The description says to read the matching GET or /schema endpoint, but does not provide any actual field information or structure, deferring entirely instead of compensating for the undocumented payload.

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?

States the verb 'Remove' and resource 'recent search', clearly indicating the action. However, it does not differentiate from sibling tools like create_search_recent beyond the obvious opposite, and doesn't clarify what a 'recent search' entry is or whether it removes all or a single entry.

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 guidance on when to use this tool versus alternatives or other remove operations. It only gives the endpoint and points to schema for payload, without explaining scenarios, prerequisites, or conditions that would select this tool.

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