get_services_summary

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

No annotations provided, so description carries full burden. Describes behavior as returning a summary of service statuses, not modifying anything. Discloses it is lightweight ('quick overview'). Sufficient transparency for a read-only, parameterless 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 conveying purpose, scope, and usage context. Front-loaded with key information. Every sentence earns its place; no 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?

Completes the picture for a parameterless tool with an output schema. Explains what it returns (counts of statuses) and when to use it (quick overview). No gaps given the context signals.

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?

No parameters; schema coverage is 100%. Description adds no parameter info (none needed). Baseline for 0 params is 4. No additional value required.

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?

Description states 'Get the global status summary across the entire service catalog — counts of operational / degraded / outage services.' Clearly specifies verb (get), resource (global status summary), and output (counts of statuses). Distinguishes from siblings like get_service by emphasizing 'global' vs. specific service drilling.

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?

Explicitly says 'Use this for a quick "is anything broken on the internet right now?" overview before drilling into a specific service.' Provides clear context and prime use case. Does not explicitly mention alternatives but implies when not to use (when needing specific service details).

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