run_query_preset

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

No annotations are provided, so the description carries the full burden. It only adds 'Auth: depends on preset query type,' which is a behavioral note. It does not disclose return values, side effects, or other execution details. The description is too sparse for a tool with no annotation support.

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 (one sentence plus metadata), which could be considered too minimal. It includes useful metadata like category and related tools. However, it lacks explanatory detail for the parameters, making it less effective despite its brevity.

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 that there are 2 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the 'limit_override' parameter, what the tool returns, or error conditions. The auth note is helpful but insufficient for complete understanding.

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?

The input schema has 0% description coverage, meaning the schema itself provides no parameter explanations. The description adds no meaning about the parameters ('name' and 'limit_override'), failing to compensate for the schema gap. This leaves the agent without understanding parameter semantics.

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's purpose: 'Execute a saved query preset.' It uses a specific verb ('execute') and resource ('saved query preset'). The related tools list distinguishes it from list_query_presets, save_query_preset, and delete_query_preset.

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?

The description includes related tools and an auth note, providing some context for usage. However, it does not explicitly state when to use this tool versus alternatives or when not to use it. The guidance is implied but not comprehensive.

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