listar_clientes

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

The annotations already declare this as readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that results span both clients and suppliers, but it does not explain pagination behavior, result limits, or what happens with empty matches, leaving behavioral gaps 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 two short sentences, front-loads the searchable scope, and ends with actionable usage guidance. There is no redundant or filler wording.

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?

With four optional parameters, rich annotations, and no output schema, the description covers the essential purpose and usage context. It could be stronger by noting pagination behavior or clarifying that listar_clientes returns both client and supplier records, but it is largely complete for this tool's complexity.

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 75%, with busca, pagina, and tamanho_pagina documented in the schema, while perfil only has an enum. The description reinforces that busca works by name or document and that results include both clientes and fornecedores, which maps to perfil, but it adds little beyond the schema about pagination or page size.

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 states a specific action ("Busca") and resource ("pessoas cadastradas (clientes e fornecedores)"), including the searchable fields name or document. It does not explicitly contrast itself with siblings such as propor_criar_cliente, though the usage sentence helps distinguish it.

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 gives clear timing guidance: use it before launching an account or registering a client. It does not state when not to use it or name an alternative lookup tool, so it falls short of the strongest usage guidance.

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