pp_get_sla_summary

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral detail beyond that: ordering ('newest first') and the fact that the return is a quantitative availability figure rather than a qualitative status.

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, purpose front-loaded, no wasted preamble. 'Instead of a guess' is slightly colorful but succinctly conveys the tool returns hard numbers, so it largely earns its place.

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 simple read-only tool with one fully-documented optional parameter and rich annotations, the description covers what it returns (monthly availability, newest first) adequately. Without an output schema there is minor ambiguity about exact return format, but nothing critical to correct invocation is missing.

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 description coverage is 100% and the single 'months' parameter is fully documented there, including its default. The description's 'per calendar month' hints at granularity but adds no new parameter meaning, so the baseline of 3 applies.

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?

States a specific resource and granularity: availability/SLA per calendar month, ordered newest first. It's clearly distinguishable from the deal/product siblings, which are all unrelated domains. The verb is implicit ('get SLA summary') but the intent is unambiguous.

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?

The scenario 'was the API down last Tuesday?' implies the appropriate usage context. However, there is no explicit when-not guidance and no named alternative sibling, leaving usage to inference.

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