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

Annotations already declare readOnlyHint true and idempotentHint true, so the safety profile is covered. The description adds value by disclosing the HTTP method (GET), pagination behavior, and optional filter parameters. However, it does not elaborate on rate limits, response size limits, or any side effects. With annotations present, this moderate addition is acceptable.

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 a single, well-structured sentence. It front-loads the core purpose ('Lista contatos') and HTTP method, then lists key details (pagination, filters). Every clause adds value, with no unnecessary words or redundancy.

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?

The tool has 8 optional parameters, pagination, and no output schema. The description covers input semantics partially but does not describe the return format, default pagination values, or response structure. For a list tool, knowing what fields are returned and how pagination works is important, and this is missing.

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 0%, so the description must compensate. It names several filters (pesquisa, idTipoContato, numeroDocumento with CNPJ/CPF hint, idVendedor, uf), adding meaning to these parameters. However, it omits three parameters (limite, pagina, account), leaving them undocumented. The description provides partial but not complete parameter semantics.

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 lists contacts (clientes/fornecedores) via GET /contatos, indicating it is a collection retrieval operation. It distinguishes itself from the sibling 'bling_get_contato' (single contact retrieval) by listing optional filters and noting pagination, making the purpose specific and unambiguous.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'bling_get_contato'. It only states the tool lists contacts with pagination and filters, but does not explain scenarios where this tool is appropriate (e.g., batch queries) or when a different tool should be chosen. No negative conditions or prerequisites are mentioned.

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