save_search

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

Indicates a write operation (mutating state) but does not disclose behavior on duplicate names, validation of params, or confirmations. With no annotations, description should offer more but is adequate for a simple save.

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?

Single sentence, no fluff, front-loaded with key action and purpose. Slightly under-informative but efficient.

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?

Missing details on return value, side effects, or error handling. No output schema or annotations, so description should compensate but does not, leaving gaps for confident agent usage.

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?

Does not explain the two parameters (name and params) beyond the schema. Schema coverage is 0%, and description adds no meaning, leaving the agent to guess what 'params' should contain.

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?

Clearly states the verb 'save' and resource 'search/pattern', and distinguishes from siblings like run_query and list_saved_searches by focusing on persistence for later reuse.

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?

Implies use when wanting to persist a search for later execution, but does not provide explicit when-to-use vs alternatives or prerequisites. Context from sibling tools somewhat clarifies but description lacks direct guidance.

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