Bulk Delete Time And Material Timecards

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

The description explicitly states the action is permanent and irreversible ('This cannot be undone', 'Permanently removes'), which aligns with the destructiveHint=true annotation. It adds context about the DELETE endpoint and the Field Productivity domain, providing behavioral insight beyond the annotation alone.

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 redundant phrases ('cannot be undone' is repeated twice) and is slightly verbose. It front-loads the purpose but could be more concise by removing duplicate statements while retaining all necessary information.

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 tool's simplicity (2 parameters, no output schema), the description provides relevant context: the API endpoint, domain (Project Management > Field Productivity), and the irreversible nature. It effectively supports tool selection without needing additional details.

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 both parameters (project_id and time_and_material_timecards_ids) with descriptions. The description adds only that project_id is required (already in schema), but does not elaborate on the format or purpose of the timecard IDs array. With 100% schema coverage, the baseline is 3.

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 is for bulk deletion of Time and Material timecards, using verbs like 'bulk delete' and 'permanently delete' and specifying the resource 'Field Productivity records'. However, it does not explicitly differentiate from sibling tools like 'bulk_delete_time_and_material_equipment_logs' or 'delete_time_and_material_timecard'.

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 notes that 'project_id' is required and indicates use for permanent deletion, implying it is for bulk operations rather than single deletes. However, it lacks explicit guidance on when not to use this tool or alternatives, leaving the agent to infer from context.

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