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

With no annotations, the description carries the full burden. It does disclose the return payload shape (text, result, validity, code) and the important side effect that include_file=true embeds a base64 PDF, which implies payload size cost. It does not say what happens if no document exists for the item, nor any auth/permission requirements.

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, no filler. The primary action and return contents come first, and the optional file-embedding flag is called out last with its exact semantics ('em base64').

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?

There is no output schema or annotations, so the description does the work of describing the return values, which it does reasonably well. However, for a tool that fetches potentially large binary payloads, it omits error cases (missing document) and confirms nothing about the relationship between diligence_id and item_id.

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 the description must compensate for three params. It explains include_file=true concretely (attaches the PDF in base64), but item_id and diligence_id receive no semantic explanation beyond their names, leaving two of three parameters undocumented.

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?

States a specific verb ('Lê') and resource ('o documento de um item'), and scopes it to either an issued certificate or an uploaded file. It also enumerates what is returned (full PDF text, result, validity, code). It does not explicitly distinguish itself from siblings like get_item, fetch_certidoes, or export_documents, so not a 5.

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?

Usage is implied by the resource scoping (reading a specific item's document), but there is no explicit guidance on when to prefer this over get_item (item metadata) or export_documents/fetch_certidoes (bulk/collection retrieval). No prerequisites or exclusions are stated.

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