check_all

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

No annotations provided, so the description must disclose behavioral traits. It mentions 'aggregate status counts' but does not explain what is counted, whether it is read-only, or any side effects or permissions needed. Lacks important operational details for a health summary tool.

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 sentences, very concise with no extraneous words. However, the lack of parameter explanation makes it incomplete rather than efficiently complete.

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 tool with no output schema, no annotations, and an undocumented parameter, the description provides only high-level purpose. Missing details on input, output, and behavioral contract.

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?

The only parameter 'category' is a string with 0% schema description coverage. The tool description does not mention or explain the parameter, leaving its purpose and allowed values entirely unclear.

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?

Describes the tool as providing 'aggregate status counts' and 'quick health summary', which clearly differentiates it from sibling tools like list_services, get_status, and get_incidents_today. The verb 'aggregate' and resource 'status counts' are specific.

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?

States the tool is for 'agents deciding whether to retry/fallback', giving clear context for when to use it. Does not specify when not to use or provide explicit alternatives, but the sibling tools imply other choices.

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