Bulk Delete Time And Material Attachments

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description reinforces permanence ('cannot be undone', 'permanently removes') and adds emphasis on the irreversible nature, which is valuable for an agent.

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 front-loaded with the core action but contains redundancy (describes permanence twice: 'This cannot be undone' repeated). Could be shortened without losing clarity.

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?

Given the simple parameter set and annotations, the description adequately covers purpose and permanence but lacks details on return values or error scenarios. No output schema exists, so that is acceptable, but the term 'Field Productivity records' might need clarification.

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 has 100% description coverage, both parameters are clearly described in the schema. The description only restates that project_id is required, adding no new semantics beyond what the schema already 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 the action ('Delete multiple Time and Material Attachments'), specifies the resource, and indicates it is a bulk operation. It distinguishes from siblings like 'delete_a_time_and_material_attachment' which handles single deletion.

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 mentions 'Use this to permanently delete...' but does not explicitly state when not to use it or provide alternatives (e.g., singular delete). The required parameter is noted, but usage context is limited.

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