Delete Project Task

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

Annotations provide destructiveHint=true, and the description reinforces that the action cannot be undone. However, it does not add significant behavioral details beyond what annotations convey, such as what happens to related data or rate limits.

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 fairly concise but contains some repetition (e.g., 'permanently delete' stated twice). It could be more streamlined but is not overly 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?

The description explains the operation and required parameters but does not mention the expected response (e.g., HTTP status or response body). Given the absence of an output schema, this is a minor gap. The description is adequate but not fully complete.

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 all three parameters with descriptions, so baseline is 3. The description adds that they are URL path parameters and mentions the endpoint, but does not provide additional semantic meaning beyond the schema.

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 'Delete project task' and specifies it is for permanently deleting Bid Board records. The verb-resource combination is precise, and while it doesn't explicitly differentiate from sibling tools like bulk_delete_project_tasks_company_v2_0, the purpose is unambiguous.

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 instructs to use this tool to permanently delete Bid Board records and lists required parameters, but it does not provide guidance on when to use this tool versus alternatives (e.g., bulk delete) or when not to use it.

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