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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds valuable behavioral context: it uses specific data sources (MITRE ATT&CK, GitHub Advisories, Cloudflare Radar), implies potential long execution (async timeout hint), and describes output contents. This goes beyond annotations.

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?

The description is three sentences, front-loaded with the core purpose and followed by input/output details and operational hints. No redundant or filler content; every sentence adds value.

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 the tool's complexity and the presence of an output schema, the description covers the essential aspects: purpose, inputs, outputs, data sources, and async behavior. It could further clarify when to choose this over siblings, but overall it provides sufficient context for an agent to select and invoke the tool.

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 only 33% (only async has a description). The description compensates by explaining service_components as 'critical components and reliability thresholds', and async as a timeout avoidance mechanism. It also implies time_window_hours with '24 hours in advance', adding meaning beyond the raw 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 a specific purpose: predict potential SLO breaches 24 hours in advance using public incident reports and MITRE ATT&CK techniques. It specifies inputs (service components, reliability thresholds) and outputs (breach probability scores, TTPs, mitigations), distinguishing it from sibling tools focused on other observability or vulnerability prediction tasks.

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 provides clear usage context: use when you need to predict SLO breaches for your service's critical components. It also gives operational guidance (pass async:true to avoid timeout). However, it does not explicitly mention when not to use or name alternative tools, though the scenario is well-defined.

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