delete_entity

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention that deletion is likely permanent, any cascading effects (e.g., the with_board option), required permissions, or the impact on associated data. The single sentence is purely functional with no behavioral context.

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 filler words, front-loading the core purpose effectively. Every word contributes meaning, making it highly concise and appropriately structured for a simple delete operation.

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?

The tool performs an irreversible action and includes a significant optional parameter (with_board) that affects behavior, yet the description provides no context about side effects, usage scenarios, or consequences. Although an output schema exists, the behavioral context is missing, making the description incomplete for an agent to safely invoke the tool.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema, but the schema already documents entity_id, entity_type, and with_board with sufficient clarity, so no deduction is needed.

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 clearly states the action ('Delete') and the target resources ('project, portfolio, or goal'), which distinguishes it from sibling delete tools like delete_macro or delete_board. However, it is brief and does not elaborate on the scope or any exclusions, so it stops short of a fully exceptional purpose statement.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of when not to use it. The description only implies usage through the resource types, and no alternative tools are referenced, leaving the agent to infer context from the parameter schema.

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