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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool is clearly a safe read operation. The description adds the detail that it performs 'ObterXML' (get XML) and supports batch, which is consistent but does not reveal additional constraints like authentication or data format. Given the annotation coverage, the description adds moderate value.

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 concise sentences with no wasted words. The bulk support note is front-loaded. Every sentence earns its place, and the structure is optimal for quick parsing.

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's simplicity and strong annotations, the description is adequate but not complete. It does not mention the return format (expected XML string) or any response structure. Since there is no output schema, the description could provide more context, making it a 3.

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 coverage is 0%, so the description carries the burden. It explains 'id' (primary identifier) and 'ids' (for bulk), but does not mention the 'account' parameter. This partial explanation helps but leaves a gap. Baseline for 0% coverage is lower, but the description compensates somewhat.

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 retrieves XML of a note by ID, with bulk support. This distinguishes it from siblings like f360_obter_danfe (which likely gets DANFE PDF) and other unrelated tools. The purpose is specific and well-defined.

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 when XML of a note is needed, especially hinting at bulk execution via 'accepts ids for batched execution.' However, it does not explicitly state when not to use it or provide alternatives (e.g., f360_obter_danfe for PDFs). The guidance is present but incomplete.

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