peaka_execute_query

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

Annotations only provide a title, so description carries full burden. 'Execute' implies mutation but no details on side effects, idempotency, error handling, or response format. Adequate but limited.

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?

Three concise sentences, front-loaded with main action. No wasted words.

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?

No output schema, but description gives sufficient context for usage. Could mention expected output (e.g., query results) but not critical given low complexity.

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 describes projectId but not queryId. Description adds that queryId is a saved query ID and tells how to find it. Compensates for the 50% coverage.

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?

Clearly states the tool executes a saved query by ID. Distinguishes from siblings like peaka_execute_sql_query (raw SQL) and peaka_get_query (retrieval).

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?

Provides explicit when-to-use guidance: use peaka_list_queries to find IDs, and if projectId unknown, call peaka_list_projects and ask user. Includes step-by-step workflow.

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