Delete Tracker entity

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuine value beyond that: 'Permanently ... irreversible' plus the cascade that with_board=true also destroys the linked agile board, and that it returns an acknowledgement. Permissions requirements are still unstated, keeping it short of 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?

Two tight sentences, front-loaded with the destructive verb and the irreversibility caveat before the optional cascade behavior. Nothing wasted.

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 3-param destructive mutation with no output schema, the description covers the key facts an agent needs: irreversibility, the entity types, the optional board cascade, and the acknowledgement return. Missing only permission/auth requirements and sibling disambiguation.

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 entity_id and entity_type are already documented; the baseline is 3. The description adds only slight nuance for with_board (project-scoped linked agile board) that the schema roughly already conveys.

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?

Specific verb+resource: 'Permanently delete a Tracker entity' and enumerates the entity types (project/portfolio/goal). However, it does not distinguish itself from sibling deletion tools such as tracker_projects_delete or tracker_boards_delete, which an agent could easily confuse with deleting a project via this generic entity tool.

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 generic entity delete versus the more specific sibling deleters, and no prerequisites or permission requirements stated. The only usage-adjacent content is the with_board opt-in, which is a parameter hint rather than routing guidance.

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