update_deal

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

Discloses auto-snapshot for undo and the rejection of blanking essential fields. With no annotations, this adds some behavioral context, but omits idempotency, permissions, or rate limits. Adequate but not comprehensive.

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 front-loaded with purpose, plus a supplementary warning. No redundancy, but could be more structured (e.g., bullet points for constraints). Efficient overall.

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?

No output schema, no annotations, 11 parameters with 0% schema coverage. Description fails to cover return values, error cases, or usage scenarios. Leaves significant gaps for a tool with moderate 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?

Schema description coverage is 0%, so description must compensate. It only mentions a few essential fields and the blanking constraint, leaving most parameters unexplained. The names are somewhat self-explanatory, but description adds minimal value.

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 'Update one or more fields on a deal' with a specific verb and resource. However, it does not distinguish from related tools like move_deal_to_stage, which is a 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?

Provides a constraint (essential fields cannot be blanked) but lacks explicit guidance on when to use this tool versus alternatives (e.g., move_deal_to_stage). No when-to-use or when-not-to-use context.

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