create_deal

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

No annotations are provided, so description carries full burden. It discloses that the tool checks for open deals and that the force parameter overrides this only after user confirmation. However, lacks details on authorization or rate limits.

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?

Three sentences in Portuguese, front-loaded with purpose. Each sentence provides essential context. Could be slightly more structured but overall efficient.

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?

Given 10 parameters, no output schema, and no annotations, the description covers key aspects: prerequisite (existing entity IDs), alternative tool, input flexibility, and the open deal check. Lacks info on return value but that's acceptable without output schema.

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 coverage is 100% (baseline 3). Description adds value by explaining that pipeline_id, stage_id, and user_id accept either names or IDs. Also hints at force parameter behavior with 'Verifica deals abertos'.

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 the tool creates deals only when person and organization already exist with known IDs, and explicitly distinguishes from create_deal_full for new leads. The verb 'Cria' and resource 'negócio' are specific.

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 explicit when-to-use (existing IDs) and when-not-to-use (new leads prefer create_deal_full). Also mentions flexibility in parameter input (name or ID) and the open deal check behavior.

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