update_query

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

Describes partial update behavior (only passed fields changed, omitted left untouched) and return value (id, name, updated_at). Annotation destructiveHint is already present, but description adds meaningful behavioral details beyond that.

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?

Three concise sentences, front-loaded with the action and key behavior. Every sentence adds value; no redundancy or fluff.

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?

Handles all aspects: what it does, how it behaves (partial update), what it returns, prerequisites, and alternative tool. Despite no output schema, the description covers enough for correct invocation.

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 has 100% coverage with descriptions for each parameter. The description reinforces the semantics by naming the fields and implying the 'omit to keep current' behavior, but does not add information beyond the schema. A slight improvement over baseline 3.

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 it updates an existing saved query and lists the updatable fields (name, SQL, description, tags). Differentiates from create_query sibling by specifying when to use each.

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 tells to find query_id via list_queries or get_query before using, and directs to create_query for new queries. Provides clear when-to and when-not-to guidance.

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