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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which covers safety. The description adds that it is paginated and supports bulk execution via empresa_ids, which is useful behavioral context beyond the schema. However, it does not describe return format, filtering, or other behavioral traits like ordering or default page size.

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 short and front-loaded with the main purpose. The bulk support note is concise and adds value. No wasted words, though it could be slightly more structured with parameter clarification.

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 there is no output schema and five parameters with no description coverage, the description is incomplete. It doesn't explain the pagination parameters (pageSize, pageNumber) or the account parameter. It also doesn't clarify the difference between empresa_id and empresa_ids, or provide any guidance on how these are used. For a list operation with bulk support, more context 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%, meaning the description provides no parameter details. The description mentions 'empresa_ids' for bulk support, which adds some meaning, but other parameters (account, pageSize, empresa_id, pageNumber) are left undocumented in the description, and the schema only provides types, not semantic meaning. The description should have compensated for the low coverage but only partially does.

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 verb ('Lista') and the resource ('inutilizações de numeração de CT-e da empresa'), and mentions pagination. It distinguishes itself from siblings by specifying the CT-e domain, though it doesn't explicitly differentiate from other list tools like hivecloud_list_ctes or hivecloud_list_dces, but the specific resource name is clear.

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 guidance on when to use this tool versus alternatives. It only mentions pagination and bulk support, but no context about typical use cases or when not to use it. No alternatives are mentioned.

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