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

The description reveals that the operation is destructive and includes a quarantine period before the slug is freed, which adds context beyond the readOnlyHint=false annotation. However, it does not disclose whether the deletion is reversible, what data or resources are removed, or what the success/error behavior is.

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?

The description is a single, lean sentence with no filler. The destructive action is front-loaded, and the parenthetical adds meaningful nuance without bloating the definition.

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 destructive tool with no output schema, the description covers the main action and one important side effect. It remains somewhat incomplete because the identifier format and quarantine/deletion details are underspecified, leaving room for misinterpretation.

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%, so the description needed to explain what the 'project' parameter should contain. The description only refers to 'a project' and mentions the slug as a side effect, without stating whether the parameter is an ID, name, or slug or providing any format examples.

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?

The description states a specific action — stop and delete a project — and adds the distinctive consequence of freeing the slug after quarantine. This is enough to differentiate it from stop_project and get_project, though it does not explicitly name those sibling tools.

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 intended use is implied: use this tool when a project needs to be stopped and permanently deleted into quarantine. There is no explicit 'when not to use' or guidance pointing to stop_project for temporary stops, leaving the choice somewhat inferential.

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