add_edge_case

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

Without annotations, the description discloses that edge case is appended to an existing entry and modifies future suggestions. It could mention whether the action is reversible or requires permissions, but overall provides good behavioral context.

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 short paragraphs with clear first sentence stating purpose. No extra words, well 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?

Given output schema exists, description doesn't need to detail return values. It covers essential usage and effect. Could hint at return type but sufficient.

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?

Schema coverage is 100% with descriptions. The description adds context by stating entry_id comes from specific tools and edge_case should be specific with details, enhancing the schema.

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 records a context where a cached solution didn't work, using specific verb 'Record a context' and resource 'edge case'. It distinguishes from siblings by referencing the search_similar workflow.

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?

Explicitly says when to call: 'Call this when search_similar returned a match but it needed modification'. Also explains the effect: appended to entry so future suggestions include caveat.

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