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

With no annotations, the description carries the full burden, and it does disclose one real side effect: a certificate not yet requested from the agency is cancelled rather than merely unlisted. It is silent on permissions, reversibility, and what happens to items already requested — significant gaps for a destructive mutation.

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 short sentences with the core action front-loaded and the conditional side effect immediately after. No filler, though the Portuguese-only wording is a minor usability tax in an otherwise English tool set.

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 two-required-param mutation with no annotations and no output schema, the description explains the action and one conditional outcome but omits parameter meaning, permission requirements, and response behavior. Adequate to start, not sufficient to call confidently.

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, yet it never mentions diligence_id or item_id, their formats, or where the IDs come from. The prose only loosely implies that both a diligence and an item must be identified.

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+resource ("Tira um documento da lista da diligência") that clearly separates it from siblings like add_document, assign_item, and remove_member. The name says "item" while the description says "documento", a small terminology drift, but the intent is unambiguous.

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 only implied: it removes a document from a diligence's list. The second sentence hints at a case distinction (a certificate not yet requested is cancelled), but no alternative tool (e.g. mark_not_applicable, retry_item) or when-not-to-use condition is named.

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