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

With no annotations, the description carries the full behavioral burden. It usefully discloses that PDFs of certidões are parsed and yield resultado/validade/código, but says nothing about permissions, size limits, duplicate handling, overwrite behavior, or failure modes for a mutation tool.

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 compact sentences with the core action and the parsing side-effect front-loaded. Each sentence earns its place, though the parsing note could be tightened.

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?

The description partially offsets the rich-but-undocumented schema by naming formats and hinting at extracted certidão fields. Still missing: parameter roles, required-vs-optional expectations, and any indication of what is returned on success or failure.

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 must compensate for five undocumented parameters. It only clarifies the file_url/content_base64 choice implicitly; item_id, diligence_id and filename are entirely unexplained, as is whether the two source params are mutually exclusive.

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 ('Anexa um arquivo') and resource (file to an item), plus accepted formats and the two upload channels. It does not differentiate itself from the sibling 'add_document', which an agent could easily confuse with an upload tool.

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?

No guidance on when to use this versus 'add_document', 'read_document', 'match_documents' or 'export_documents'. The choice between file_url and content_base64 is stated as an option but with no conditions for picking one.

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