get_saved_query

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

No annotations are provided, so the description must carry full behavioral disclosure. It only says 'Get', which implies a read-only operation, but provides no details on error behavior, caching, or lack of side effects. This is minimal and leaves the agent to infer behavior.

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 a single concise sentence, front-loaded with the action and resource. Every word is necessary, and there is no unnecessary detail or repetition.

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 simple get-by-ID tool, the description adequately states the core function, but it does not describe the return value or behavior when the ID does not exist. The absence of an output schema makes this gap more noticeable, though the tool's simplicity mitigates the impact.

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 schema provides no descriptions for query_id (0% coverage), but the parameter name is self-explanatory. The description's 'by ID' clarifies that the integer is the identifier, but adds little beyond what the parameter name already conveys. It does not specify constraints or format.

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 uses the specific verb 'Get' and identifies the resource as 'saved query' with clear scope: 'one by ID'. This distinguishes it from sibling tools like list_saved_queries (which returns all) and create/update variants, making the purpose unambiguous.

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 implies use when a specific saved query ID is known, but it does not explicitly mention when to use this over list_saved_queries or how to handle non-existent IDs. No alternative tools are referenced, so guidance is limited.

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