get_service_day_rollup

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

No annotations are provided, so the description carries the full burden. It describes the outputs (uptime, impact windows, incidents) and the input format, but does not disclose whether the operation is read-only, any required permissions, or potential performance considerations.

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, no fluff, front-loaded with the main action. Every sentence adds value, including the example usage.

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?

The tool has an output schema, so return values are covered. The description provides sufficient context about what the tool returns (uptime, impact windows, incidents) and the input constraints. For a simple rollup tool with two parameters, the description is complete.

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 0%, so the description must compensate. It adds meaning for the 'date' parameter (UTC calendar day, ISO YYYY-MM-DD) and implies 'slug' is the service identifier via the example. However, it does not fully describe all parameter details.

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 the action (get a one-day rollup), the resource (catalog service), and the specific outputs (aggregated uptime, per-component impact windows, incidents). It also provides an example query, which distinguishes it from sibling tools like get_service_uptime or list_service_incidents.

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 description explicitly tells when to use the tool: to answer 'what happened to Stripe on 2026-06-01?'. However, it does not explicitly mention when not to use it or provide alternatives among the sibling tools.

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