patch_lead

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

No annotations; description only mentions PATCH method and partial update, failing to disclose permissions, idempotency, or effects on omitted fields.

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?

Single, well-front-loaded sentence plus instruction; no unnecessary words.

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?

Despite output schema, no annotations and low schema coverage mean description should provide more context; missing prerequisites, parameter details, and result description.

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 has 0% description coverage; description mentions 'status or assignment' mapping to optional params, adding some meaning but lacking formats or constraints.

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?

Description clearly states 'partially update a lead status or assignment' and distinguishes from 'update_lead' for notes, making purpose specific and differentiating from sibling.

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?

Explicitly directs to use 'update_lead' for notes, implying this tool is for status and assignment; provides clear context but no further exclusions.

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