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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds pagination and bulk execution context. However, it does not disclose return-shape expectations, pagination defaults, or how parameters like account and empresa_id influence results.

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, front-loaded, and immediately identifies the resource and behavior. The bulk-support notice is useful and concise, with minimal 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?

For a read-only list tool, the description is minimally viable, but the lack of output schema increases the burden on the description. It provides no details on response format, default pagination, or the relationship between singular and plural empresa parameters, so the agent is left guessing at meaningful behavior.

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%, and the description only compensates for two of the five parameters: empresa_ids (batch support) and pagination via 'paginated'. The meaning of account, single empresa_id, pageNumber, and pageSize are left unstated, and relationships/requirements among the parameters are 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 action ('Lista') and the resource (DC-e / Declaração de Conteúdo Eletrônica), with company scoping and pagination noted. This distinguishes it from sibling tools such as hivecloud_list_ctes and hivecloud_list_mdfes.

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 use case is implied: use this tool to list DC-e records from the company, with pagination and bulk execution via empresa_ids. No explicit guidance is given about when to prefer this over alternatives or which parameter combination to use.

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