lead_enviar

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

With no annotations, the brief description fails to disclose behavioral traits like idempotency, authentication needs, or side effects. It does not indicate whether duplicate leads are handled or what happens after sending.

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?

The description is a single short sentence, but it is under-specified rather than concise. It lacks structured breakdown and does not earn its place by providing essential information.

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 the complexity of a nested parameter object and no output schema, the description is severely incomplete. It does not explain return format, error conditions, or how to structure the input correctly.

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?

The input schema has 0% documentation coverage on properties, and the description adds no meaning to the parameters. The nested object 'dados' with fields Nome, Email, Telefone is not explained, leaving the agent without guidance on required vs. optional fields.

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?

The description 'Envia lead de fonte externa' (Sends lead from external source) clearly specifies the verb and resource, and distinguishes from sibling tools like 'leads_pesquisar' (search leads). However, it lacks detail on what 'lead' and 'external source' mean precisely.

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?

No guidance is provided on when to use this tool versus alternatives such as 'cliente_cadastrar' or 'leads_pesquisar'. There is no mention of context, prerequisites, or exclusions.

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