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

The description says 'Permanently delete' which discloses irreversibility, but with no annotations provided, the description carries the full burden. It doesn't disclose side effects, cascading deletions, auth requirements, or what happens to associated data. The word 'permanently' adds some value but leaves significant behavioral gaps.

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 short sentence with no waste. It is front-loaded with the action and resource. However, it is so brief that it misses opportunities to add behavioral context.

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 destructive tool with no annotations and no output schema details, the description is incomplete. It doesn't explain return values, error conditions, or side effects. An agent would not know what to expect after calling it or what prerequisites exist.

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 the schema already documents both parameters. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb ('delete') and resource ('entity'), and the title reinforces it. It is clear what the tool does, though it doesn't explicitly distinguish itself from sibling delete tools (delete_dataset, delete_project, etc.) beyond the resource name.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention that deletion is permanent, irreversible, or that related resources may be affected. The description simply states the action without context.

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