Get cache metrics

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destructiveness. Description adds no further behavioral context (e.g., does it aggregate data? returns historical snapshots?). Meets the minimum by not contradicting 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?

Single sentence, no filler. Every word is necessary and front-loaded. Perfectly concise for a straightforward metrics retrieval tool.

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?

Given the tool's simplicity, good annotations, and complete parameter schema, the description is nearly sufficient. However, it lacks a hint about the output (e.g., what metrics are returned: hit rate, latency? ). Slight gap reduces from 5.

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 documentation covers both parameters fully (100% coverage). Description does not add extra meaning beyond the schema's description of 'Cache ID' and period examples. Baseline score due to complete schema.

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?

Clear verb 'Get' and resource 'metrics for a specific cache'. Distinct from sibling tools that retrieve metrics for other resources (e.g., environment, database clusters, websockets). No ambiguity.

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?

No guidance on when to use this tool versus similar metrics tools (e.g., for environments, databases). Does not state required context (e.g., cache must already exist) or when to choose this over other get_*_metrics endpoints.

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