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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavioral context: it queries official third-party status pages, covers outages only, and explicitly excludes throttling/per-account limits. No auth or rate-limit detail, but the safety and scope profile is well covered.

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?

Three dense sentences, front-loaded with the purpose before the exclusions and parameter rules. The provider enumeration is slightly crammed into a single line, but nothing is redundant or padding.

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 one-parameter, read-only tool with no output schema and annotations covering safety, the description supplies the source list, the exclusion rule, and the parameter contract. A brief hint at return shape (per-provider status objects vs. a flat incident list) is the only real gap.

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% and the schema has no enum, so the description carries the full load — and does: it lists every accepted provider value, notes a tool id is also valid, and specifies that omission returns all providers. This is exactly the information the schema omits.

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 verb+resource ('Live operational status and open incidents') and enumerates the exact sources it covers (Anthropic, OpenAI, Cursor, GitHub Copilot, Google, Windsurf). An agent can immediately tell this is a vendor-status reader, distinct from the plan/route siblings.

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?

Gives a clear negative scope rule ('Outages only: it does not detect throttling or per-account limits') and the default behavior ('omit for all'), which tells the agent when this tool is the wrong choice. It stops short of an explicit trigger like 'call this when a provider call fails', but no sibling competes for the same job.

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