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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds the endpoint and the term 'multiattendance', but it does not disclose additional behavioral aspects such as pagination, result size limits, or authentication requirements. Since annotations cover safety, a baseline 3 is appropriate.

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 concise sentence that includes the endpoint, which is useful. However, it lacks additional context that would be expected, but it is not verbose or wasteful.

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 0% schema coverage and no param explanations, nor behavior details beyond annotations, the description is minimal. The tool has two parameters and no output schema, so more explanation is needed to make it usable, especially since 'multi' is ambiguous.

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%, meaning the description must explain the parameters 'query' and 'account', but it does not. No additional meaning is provided beyond the schema's raw type declarations. This is a significant gap.

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 'Buscar atendentes (multiatendimento)' (Search attendants (multi-service)) and identifies the HTTP endpoint, but does not clarify what 'multi' means or how it differs from other attendant list tools like datacrazy_attendants_crm_list. The purpose is partially clear but lacks specificity to distinguish it from siblings.

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 context is provided about when to use this tool versus alternatives. It mentions the endpoint but not any conditions or use cases. The description does not guide the agent on choosing between this and other attendant-related tools.

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