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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read operation. The description adds that it is paginated and that filters accept specific fields (cpf_cnpj, situacao, idVendedor), which is useful context beyond annotations. No contradiction.

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?

Description is concise (two sentences) and front-loaded with the primary action and pagination info. No waste, but could be more structured with parameter details.

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 4 parameters, 0% schema coverage, no output schema, and no enum hints, the description is reasonably informative but incomplete. It covers key search and filter semantics but omits 'page' and 'account', and no return format is mentioned (though output schema is absent, so the description should at least hint at return behavior). The annotations mitigate some completeness needs.

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 has 0% description coverage, so the description must compensate. It explains 'search' (search by name) and 'filters' (JSON with accepted fields), but 'page' and 'account' are left undocumented. The description adds meaning for two of four parameters, but the other two remain 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 lists contacts with pagination, and the name 'tiny_list_contacts' is specific. It distinguishes from sibling tools like 'tiny_get_contact' by implying a list/search operation, but doesn't explicitly compare to 'tiny_get_contact' or other list tools.

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 implies usage for searching contacts by name or filters, but provides no guidance on when to use this tool versus alternatives like 'tiny_get_contact' for single contact retrieval. No explicit when-to-use or when-not-to-use scenarios are given.

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