atualizar_conta

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

No annotations are provided, so the description carries full burden. It only states that the tool updates information, but does not disclose side effects, authorization requirements, error handling, or any behavioral traits beyond the obvious mutation.

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 concise with two sentences and a bullet list. It is well-structured, front-loading the purpose. No wasted words, though it could be slightly more organized.

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 simple update tool with 3 parameters and no output schema or annotations, the description provides basic context. It covers prerequisite and parameter format but lacks return value, error cases, and behavioral details. Adequate but not comprehensive.

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%. The description adds meaning only to the 'dados' parameter, calling it a dictionary of fields to update. The 'id_conta' and 'nome' parameters are not explained beyond their types and names, leaving their semantics partially unclear.

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 tool updates account information in Ploomes CRM. The verb 'Atualizar' and resource 'conta' are explicit. However, it does not distinguish from sibling tools like 'buscar_conta' or 'excluir_cliente' beyond the natural action difference.

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 provides a prerequisite instruction to use 'buscar_conta' to get the ID, and explains that 'dados' is a dictionary of fields to update. However, it lacks explicit when-to-use guidance, exclusions, or alternatives beyond the single prerequisite.

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