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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them by enumerating the full blast radius (monitors, incidents, check history, maintenance windows, status pages with custom domain certificates, alert rules, API keys) and stating irreversibility. The last-project-of-organization restriction is a business rule not expressible in any structured field, making this genuinely additive.

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 action and scope, then the consequence list, then the hard constraint. Two sentences, no filler, and every clause carries information an agent needs before committing to an irreversible call.

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 single-parameter destructive tool with no output schema, the description covers what matters most: cascade effects, irreversibility, and the deletion guard. It is silent on permission requirements and on what an error looks like if the project does not exist, which are minor gaps given the annotation coverage.

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 the single parameter already carries "ID of the project to delete". The description only restates "by ID" and adds no format, type, or sourcing detail (e.g., where to obtain the ID via list_projects), so baseline 3 applies.

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 ("Delete a project by ID") and immediately enumerates the contained entities removed with it, which distinguishes it from the many sibling delete_* tools (delete_monitor, delete_status_page, delete_alert_rule). An agent can tell exactly what scope this tool operates at 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?

Gives a clear use condition and an explicit exclusion: the last project of an organization cannot be deleted. What it lacks is routing to alternatives — it never says to use delete_monitor or delete_status_page when only a child resource should be removed, leaving the agent to infer that from the cascade list.

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