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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. Description adds the bulk execution behavior, though it doesn't disclose any other quirks like pagination or limits. No contradiction with 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?

Two sentences, front-loaded with the purpose and endpoint, no wasted words. Perfectly sized.

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?

Tool is simple with no output schema, but annotations cover safety. However, description fails to explain the 'query' and 'account' parameters, and does not describe the response format. For a tool with 0% schema coverage, more is needed.

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%, so description must compensate. It mentions 'id' and 'ids' but not 'query' or 'account'. No explanation of what these parameters do beyond the schema names. This is a significant gap for a 4-parameter tool.

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?

Purpose is clearly stated: 'Buscar atendente por ID (multiatendimento)' with HTTP endpoint, and it mentions bulk support via 'ids' parameter. It distinguishes from sibling datacrazy_attendants_crm_get by the 'multi' qualifier, though it doesn't explicitly contrast with the sibling.

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 fetching attendants by ID, but does not provide explicit guidance on when to use this tool versus alternatives like datacrazy_attendants_multi_list or datacrazy_attendants_crm_get. Bulk support is mentioned but no conditions are given.

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