fields_bulk_delete_deal_fields

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

No annotations provided, so description must carry behavioral disclosure. Describes input normalization but does not mention consequences of deletion (e.g., irreversibility, cascading effects on deals), return behavior, or error handling.

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?

Two sentences, directly states action and input formats. Efficient and front-loaded with no unnecessary 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?

For a simple bulk delete with one parameter and no output schema, the description covers input format and normalization but lacks details on operation outcome (e.g., whether it succeeds/fails per field, return value). Adequate but incomplete.

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 covers 100% of parameters with description. The description adds normalization behavior ('Both shapes are normalized to Pipedrive's expected ?ids= query parameter'), providing value 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?

Clear verb 'delete' and resource 'multiple custom deal fields' with 'in a single request' distinguishing from individual deletions. Sibling tools with similar bulk delete for other entities are differentiated by the resource name in the tool name.

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?

States the operation and input formats but does not provide when to use vs alternatives (e.g., individual field deletion) or prerequisites for deletion. Implicit usage context only.

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