queries_update

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

Description states 'Update' which aligns with annotations (readOnlyHint: false). However, no additional behavioral context is provided beyond the obvious write operation. No information about partial update semantics, required permissions, or error conditions.

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?

The description is very short (four words). While concise, it under-specifies for a tool with 12 parameters. However, it is not verbose.

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 the tool has 12 parameters, low schema coverage, and a declared output schema (not described), the brief description is insufficient for an agent to fully understand the tool's behavior and return values.

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 description coverage is 42% (low), but the description adds no meaning to any parameter. It does not explain which fields are updatable, required, or any relationships among parameters.

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?

Description states 'Update a saved SQL query' which is a specific verb and resource. It clearly distinguishes from sibling tools like queries_create, queries_get, queries_list, and queries_delete.

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. Does not mention any context or exclusion criteria.

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