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

The description aligns with the readOnlyHint and idempotentHint annotations by presenting a read-only status lookup. It adds useful behavioral context such as 'public monitored target' and 'No API key needed', though it does not explicitly state side-effect-free behavior; annotations already cover this.

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 concise sentences with no redundant wording. The description front-loads the tool's purpose, then lists the included data points, and finishes with the URL-derived parameter guidance.

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 simple two-parameter input and no output schema, the description sufficiently explains both how to call the tool and what will be returned. It covers the key output categories and necessary context for selecting this 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 100% and both owner and slug parameters are explained. The description adds the practical hint to take these values from the status page URL, but does not materially expand beyond the schema's existing parameter descriptions.

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 ('current status') and resource ('public monitored target'), and enumerates the exact data returned (overall state, uptime, last check, nightly scores, open incidents, badge/status URLs). It is clearly distinguishable from sibling tools like list_incidents or run_now.

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?

Provides clear context on when to use the tool: to retrieve status for a public monitored target using owner and slug from a status page URL, and notes no API key is needed. It does not explicitly contrast with sibling tools, but the scope is clear enough for an agent to select it appropriately.

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