peaka_refresh_materialized_query

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

Annotations already indicate non-read-only (readOnlyHint false) and non-destructive (destructiveHint false). Description adds that it triggers a refresh and requires prior calls, but does not detail side effects or async 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?

Concise two-paragraph structure, front-loaded with purpose, followed by essential details. Every sentence adds value without redundancy.

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?

Adequate coverage of prerequisites and action, but missing any mention of return values or async nature since no output schema exists. Could be slightly more 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?

Schema coverage is 100%, but the description adds procedural context (e.g., 'Use the queryId returned from peaka_list_queries for queries whose queryType is "MATERIALIZED"' and workflow for projectId), enhancing usability beyond schema descriptions.

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 'Trigger a refresh on a materialized saved query' with a specific verb and resource, and distinguishes from siblings like refresh_cache by specifying the query type.

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 guidance on prerequisites (projectId, queryId from peaka_list_queries for MATERIALIZED type) and instructs to call peaka_list_projects if projectId is unknown. Lacks explicit 'when not to use' but clear enough.

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