Save search

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

Annotations only declare the generic write profile (readOnly=false, non-idempotent, open-world); the description adds real behavior: the alert goes to this account only, edits silently preserve the existing filters, and accounts are capped at 10 saved searches. The 10-search cap and the filter-immutability constraint are exactly the kind of side effects an agent would otherwise discover by failing.

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?

Front-loaded with the two-mode split, and every sentence carries information (defaults, cap, filter preservation). The middle sentence is long and packs create-behavior, title, filters and alert into one run-on, which costs a point on readability.

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?

For a 9-parameter create-or-update tool with no output schema, it covers both invocation modes, what gets mutated versus preserved, who receives the alert, and the account-level quota. Nothing an agent needs to call this correctly is missing.

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%, so baseline is 3; the description earns an extra point by explaining the mode dependency of parameters, i.e. that filters and query are create-only and are ignored-by-design on update. It doesn't restate the enum values or defaults, but it doesn't need to.

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 a specific verb and resource ("Save a project search") and immediately covers both modes: create with an email alert, or rename / change alert frequency on an existing search. An agent can distinguish this from list_saved_searches and delete_saved_search without opening the schema.

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 gives the selection rule: no saved_search_id creates a new search, with saved_search_id edits the title and alert only. It also names the alternative path when filters need to change ("make a new search for other filters and delete the old one"), which routes the agent away from a misuse of this tool.

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