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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds real value beyond that: it specifies the blast radius (project plus saved pipeline document), the effect on the user's project list, and explicitly that already-run executions are unaffected. It doesn't cover auth/permission requirements, which would be needed for a 5.

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?

Three short sentences with the destructive action front-loaded, then the hard prerequisite, then the consequence note and id source. Every sentence carries information; nothing is padding.

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?

An output schema exists so return values need not be described. The description covers the destructive scope, the confirm gate, the non-effect on prior executions, and where to get the id — everything an agent needs before invoking an irreversible delete.

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%, so both parameters are already documented, including the confirm guard ('MUST be true to delete'). The description's 'Requires confirm=True' and 'Find ids with project.list' restate rather than extend the schema, so the baseline 3 is appropriate.

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') plus the scope of what is deleted ('and its saved pipeline document') and the location ('from the studio workspace'). This clearly differentiates it from sibling project.create/project.list/project.load/project.save without the agent needing to open any 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 an explicit prerequisite ('Requires confirm=True') and routes the agent to project.list for obtaining ids, which is genuine when-to-use guidance. It stops short of naming when *not* to use it or an alternative deletion path, so it falls short of a 5.

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