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

With annotations already indicating readOnlyHint=false, the description's '[write, altera dados]' tag adds no new behavioral information. It discloses the HTTP endpoint but not consequences, required authentication, response behavior, or error conditions, so it provides minimal value beyond the annotations.

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 short and front-loaded, but it repeats the mutation signal already present in annotations with '[write, altera dados]'. It is concise yet under-specified, so the brevity is not fully useful.

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 two-parameter tool with no output schema, the description still lacks essential context: the payload format for 'body', the role of 'account', and when this endpoint differs from datacrazy_leads_create. The annotations and sibling names provide some orientation, but the description does not make the tool safely invocable.

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% and the description does not explain what 'body' or 'account' mean. 'Campos adicionais' hints at the purpose of body but gives no structure, format, or example, forcing the agent to guess how to construct a valid request.

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 clearly states the action ('Criar lead') and the specific resource ('campos adicionais', POST /api/v1/leads/additional-fields). It also distinguishes this from the sibling datacrazy_leads_create by emphasizing additional fields, though it doesn't explicitly contrast them.

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 about when to use this tool versus alternatives like datacrazy_leads_create. The description implies 'use when creating a lead with additional fields,' but it does not state prerequisites, exclusions, or when the normal lead creation tool would be preferred.

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