Delete Work Activity

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

Annotations already indicate destructive and idempotent behavior. The description reinforces this with 'cannot be undone' and 'permanently removes,' adding value by specifying the restriction on Procore-provided activities and providing the API endpoint.

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 relatively short but contains repetition: 'This cannot be undone. Permanently removes the specified Incidents. This action cannot be undone.' Could be more concise, but it is front-loaded with the core action.

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 simple delete operation, the description covers the essential aspects: action, restrictions, required parameters, and endpoint. No output schema exists, but the return value is implied as empty or success.

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?

With 100% schema description coverage, the schema already documents both required parameters (company_id, id). The description merely lists them as required and adds endpoint info, but does not add new semantic meaning beyond what the schema provides.

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 it deletes a Work Activity and distinguishes from siblings like create, update, list, and show by specifying the delete action and noting that Procore-provided activities cannot be deleted.

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 provides clear usage context: it permanently deletes Incidents and cannot be undone. It also notes that Procore-provided Work Activities cannot be deleted, which is a specific limitation. It does not explicitly mention alternatives, but the delete verb is unambiguous.

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