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

Annotations flag destructiveHint and idempotent, but the description supplies the actual blast radius: a site takes its content, dependency and cron rows with it; a group alone moves its items to top level unless group_contents=remove; the underlying sites and checks stay monitored. That is exactly the context the destructive flag cannot convey.

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?

Front-loaded with the selection trigger, then consequence, then return value, then exclusion — a sensible order. Four dense sentences with no filler, though the group_contents sentence partially duplicates the schema's own description.

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?

No output schema exists, and the description compensates by stating 'Returns what was removed and the page's components after.' Combined with scoping rules and the monitoring-continues caveat, an agent has everything needed to call this safely on a destructive operation.

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, and the schema already spells out group_contents in detail. The description still adds value by explaining the consequence of each component kind (site carries rows, group alone relocates items, check is just removed), but its group_contents wording largely restates 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?

Starts with a specific verb and resource: 'a site, check or group heading taken off one of their public status pages.' It also enumerates the three component kinds, which lets an agent distinguish this from update_status_page_component and add_status_page_component without reading schemas.

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?

Explicit when-to-use ('when the user wants ... taken off a public status page') and explicit when-not ('Not for deleting a site, a check or the page itself, which is done in the dashboard'). It also supplies the side-condition that monitoring continues, which prevents an agent from reaching for a delete tool instead.

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