peaka_get_query

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

Annotations already mark readOnlyHint=true, so the read-only nature is clear. The description adds value by detailing the returned fields (displayName, inputQuery, queryType, auto-refresh schedule). It does not contradict annotations.

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 two short paragraphs: first states purpose and return fields, second gives actionable workflow guidance. No extraneous information; every sentence earns its place.

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 read tool with no output schema, the description covers what the tool returns and how to obtain required parameters. It lacks error scenario details but is sufficient given the tool's simplicity.

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 coverage is 100% (both parameters described in the input schema). The description does not add extra parameter-level semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 starts with 'Read a single saved query by its ID,' which clearly states the action (read) and the resource (saved query). It lists return fields (displayName, inputQuery, queryType, auto-refresh schedule), distinguishing it clearly from sibling tools like peaka_execute_query or peaka_delete_query.

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 provides explicit guidance: if projectId is unknown, call peaka_list_projects first and ask the user; remember the chosen projectId. It also hints that queryId comes from peaka_list_queries. This leaves no ambiguity about prerequisites and when to use the tool.

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