add_deal_field

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

Discloses 'Returns the new field's id and key to use in update_deal(custom_fields={key: value})' and 'Auto-backed up.' Since no annotations exist, this provides needed behavioral context, though permissions and rate limits are omitted.

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?

Brief, uses bullet points effectively, front-loaded with main action. Every sentence adds value with no fluff.

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?

Covers purpose, parameters, output, and backup behavior. Missing details on error handling or account limits, but adequate for a creation tool given the complexity.

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 0% schema coverage, the description adds essential meaning: lists allowed field_type values and explains options are for enum/set dropdown fields. This fully compensates for lacking schema descriptions.

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?

Clearly states 'Create a new custom deal field on the Pipedrive account' with specific verb and resource. Distinguishes from siblings like remove_deal_field and list_deal_fields by focusing on creation.

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?

Provides practical info about field types and options but does not explicitly guide when to use vs alternatives (e.g., when to add vs remove or list fields). Lacks prerequisites or exclusion criteria.

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