Delete Project Task

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by emphasizing irreversibility ('This cannot be undone' repeated) and providing the exact REST endpoint, which gives context beyond annotations.

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 contains redundancy: 'This cannot be undone' appears twice. It also includes endpoint details which, while useful, could be integrated more concisely. The structure is front-loaded but slightly verbose.

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 operation with no output schema, the description covers key aspects: purpose, permanence, required parameters, and API location. It lacks information about return values or prerequisites, but the endpoint and destructive nature are sufficiently explained.

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 coverage is 100% with descriptions for each parameter. The description merely lists the required parameters without adding new semantic detail, so it meets but does not exceed the baseline.

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 tool's function: 'Delete project task' and 'permanently delete the specified Estimating records.' It distinguishes itself from siblings like bulk deletes or v2.0 endpoints by specifying the exact resource and API endpoint.

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 description says 'Use this to permanently delete the specified Estimating records' and lists required parameters, but it does not offer guidance on when to use this tool versus alternatives like bulk_delete_project_tasks_company or v2.0 version. Missing explicit when-not or alternative tool references.

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