cliente_detalhes

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only implies a read operation but does not confirm read-only nature, required permissions, pagination, or potential side effects. This is insufficient.

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 at one sentence. While not verbose, it lacks necessary depth. Front-loading is not an issue as the entire description is front-loaded, but the content is insufficient for an effective tool definition.

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 tool has a required parameter, no output schema, and no annotations, the description is far from complete. It omits return format, error conditions, and relationship to other client tools, leaving the agent underinformed.

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 low (50%: 'campos' described, 'codigo' not). The description adds no parameter information beyond the schema. It does not explain the purpose of 'codigo' or how 'campos' filters results, offering no added value for parameter understanding.

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 'Info completa do cliente' indicates the tool retrieves complete client information. It distinguishes from sibling tools like 'cliente_favoritos' or 'clientes_pesquisar' but uses vague wording ('completa') without specifying what data is included.

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 usage guidance is provided. The description does not specify when to use this tool versus alternatives like 'cliente_alterar' or 'clientes_por_corretor', nor does it mention any prerequisites or context.

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