fluig_process_attachment_download

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

With no annotations, the description carries the full burden. It does add genuine behavioral context that structured data lacks — the deliberate use of the singular route to avoid the plural route's @QueryParam('user') bug — which is real transparency. However, it omits key behaviors for a write-to-disk operation: whether an existing file at destino is overwritten, what is returned on success, size/encoding limits, and auth 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, front-loaded with the action and followed by the caveat. Both earn their place, though the @QueryParam bug detail is implementation trivia that could be compressed to 'use the singular route; the plural route ignores replacedUser'.

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 4-required-parameter file-writing tool with no annotations and no output schema, the definition covers the action and the path sandboxing (via schema) but leaves the return value and overwrite/error semantics unstated. Adequate to invoke, not complete enough to predict the effect.

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 100%, so all four parameters are already richly documented, including the env enum rationale and the FLUIG_SAIDA_DIR sandbox rule. The description adds no parameter meaning beyond the schema; the route-parameter discussion concerns user/replacedUser, which are not even inputs here, so it adds noise rather than semantics.

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 and resource ('Baixa o BINÁRIO de um anexo de solicitação') plus the destination form (local file), which is precise enough to distinguish it from list-style siblings. It does not explicitly contrast itself with other download-flavored siblings such as fluig_ged_download or fluig_process_attachments, so full differentiation is left to inference.

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: the agent can infer 'use this when you need the attachment bytes on disk', and the schema note points to fluig_process_attachments for the sequence. There is no explicit when-to-use/when-not, no prerequisite call ordering, and no mention of the sibling download tools.

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