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

The description only repeats that it modifies data ('altera dados') without detailing side effects, reversibility, or consequences. Given it is a write operation, more transparency is expected; annotations already indicate non-read-only, so this adds little.

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 extremely concise, using two short sentences. It avoids unnecessary verbosity and directly states the purpose and bulk capability, which is appropriate for the simplicity of the tool.

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 that the schema lacks any descriptions (0% coverage), the description should compensate by explaining the purpose of each parameter. It only mentions ids, leaving id, body, and account unexplained, making it incomplete for a user to fully understand the tool's usage.

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 four parameters (id, ids, body, account), but the description only references 'ids' for bulk support. It does not explain id, body, or account, leaving most parameters undefined.

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 'Atualizar lead' (update lead) and the HTTP method PATCH, distinguishing it from create, delete, and list operations. It does not elaborate on specific fields, but the verb+resource pattern is 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?

The description mentions bulk support for batched execution, providing some guidance for when to use multiple ids. However, it does not explicitly state when to use this tool versus alternatives, such as when a lead already exists or when to avoid it.

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