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

With no annotations provided, the description carries the full burden and does well: it declares read-only behavior, unauthenticated/free access, the precise API path, and the shape of returned fields. It stops short of disclosing rate limits, pagination behavior, or what happens for non-Statuspage URLs or network failures.

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, front-loaded with the read-only signal and the core action, then packed with the endpoint and return-field detail. No filler or redundant restatement of the tool name.

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?

With no output schema, the description correctly compensates by enumerating the returned fields (name, status, impact, created_at, resolved_at, shortlink). It is complete for a simple two-parameter read tool, with only operational edge cases (invalid host, rate limiting, truncation by limit) unaddressed.

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 coverage is 100%, so the baseline is 3, but the description adds real value by clarifying that page_url is a base URL onto which <base>/api/v2/incidents.json is appended, preventing an agent from passing a full endpoint path. The limit parameter is left entirely to the 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?

States a specific verb and resource ("fetch recent incidents") plus the exact source class (Atlassian Statuspage-hosted pages) and the underlying endpoint. An agent knows precisely what will be returned and from where without opening the schema.

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 scopes applicability clearly: the target must be a public, Statuspage-hosted page served over https, and no credentials are needed. It does not discuss when to prefer an alternative source, but there are no sibling tools and the hosting constraint effectively serves as the exclusion criterion.

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