performance_get_cache_performance_status

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

Describes what metrics are returned but does not state whether the tool is read-only or has side effects. No annotations provided to fill the gap, leaving behavioral uncertainty.

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?

Two short paragraphs plus a returns line, each sentence serving a purpose: stating purpose, detailing metrics, suggesting use, and listing output structure. No 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?

Given no parameters and an output schema, the description covers the essential context: what metrics are provided and why to use it. Minor gap: no mention of prerequisites or cache scope.

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?

Tool has no parameters (schema coverage 100%), so the description adds value by explaining the output metrics, which helps the agent understand what to expect beyond the 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?

The description clearly states it provides cache performance metrics and optimization suggestions, but does not explicitly differentiate from sibling tools like performance_get_database_performance_status or performance_get_redis_health_status beyond naming.

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 a use case ('to optimize caching strategies and identify cache bottlenecks') but lacks explicit when-not-to-use guidance or comparison to alternative performance tools.

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