Delete Multiple Signatures

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

The description emphasizes the permanent nature of the deletion ('This cannot be undone', 'Permanently removes'), which aligns with the destructiveHint annotation. It also provides the API endpoint and context about Field Productivity. This adds value beyond annotations by clarifying the irreversible effect and the scope of records affected.

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 short but contains redundancy: 'permanently delete' and 'This cannot be undone' are repeated. Every sentence earns its place, but the repetition makes it slightly less concise.

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 that this is a bulk delete operation with no output schema, the description should mention what the response looks like (e.g., success message) or any error conditions. It only covers the input and permanence. Lacks completeness for an agent to fully understand the tool's behavior.

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%, so baseline is 3. The description only restates that 'project_id' is required, which is already in the schema. No additional explanation for 'time_and_material_signature_ids' is provided, but the schema descriptions are sufficient.

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 signatures for specified IDs, specifically for Field Productivity records. The verb 'deletes' and resource 'signatures' are precise. The title 'Delete Multiple Signatures' distinguishes from siblings like 'delete_a_signature' which targets individual items.

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 explicitly says 'Use this to permanently delete the specified Field Productivity records' and notes the required parameter. While it doesn't explicitly state when not to use or mention alternatives, the context of bulk vs single delete is clear from the name and siblings. Implicitly guides that this is for multiple deletions.

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