crm_create_deal

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

No annotations are provided, so the description carries the full burden. It mentions the tool 'sets' value, stage, and links to lead, indicating mutation, but does not disclose side effects, required permissions, prerequisites (e.g., lead must exist), or behavior when lead_id is empty. Lacks detail for a mutation tool.

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?

A single, efficient sentence that front-loads the action. Every word carries meaning, but the structure is flat with no additional contextual layers.

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 tool with 5 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the purpose of owner_id, the scenario when lead_id is absent, the return value, or how it differs from crm_move_deal. An agent would need to infer important details.

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 the description must compensate. It mentions value, stage, and lead_id indirectly, but does not explain the meaning of 'name' or cover 'owner_id' at all. The schema provides types/defaults but no descriptions, and the description adds little beyond what the schema already exposes.

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?

States a specific verb (create), resource (deal/opportunity), and source (from a lead). It also lists the key fields it sets (value, stage, links to lead). Clearly differentiates from siblings like crm_create_lead and crm_move_deal.

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?

Implies usage by describing the action (create a deal from a lead), but does not explicitly state when to use this tool instead of alternatives like crm_move_deal or crm_create_lead. No exclusions or conditions are given.

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