get_query_result

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

The description adds that the tool returns results, which is inherent to its purpose. The annotation 'readOnlyHint: true' already indicates read-only behavior, so the description offers minimal extra transparency beyond confirming output.

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, front-loaded sentence that conveys essential information without unnecessary words 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?

For a straightforward read-only query execution tool with well-documented parameters and no output schema, the description covers the basic functionality. It could mention error handling (e.g., missing query ID) but is generally complete.

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 covers all 4 parameters with descriptions (100% coverage), so the description does not add new semantic detail. It merely restates the schema's intent.

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 'Execute a saved query by ID and return results,' specifying the verb (execute), resource (saved query), and outcome (return results). This distinguishes it from siblings like 'run_query' (executes arbitrary SQL) and 'list_queries' (lists saved queries).

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 the tool is for executing previously saved queries, but provides no explicit guidance on when to use it versus alternatives like 'run_query' or 'smart_query'. No when-not-to-use or alternative names are given.

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