Baixar um arquivo arbitrário do SIGAA

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

With no annotations provided, the description carries the disclosure burden and does so well: it reveals side effects (saves file to disk, returns path), and it describes defensive behavior (detects and rejects error/session-expired pages disguised as files via redirect or Content-Type text/html). Missing details are limited to session/auth prerequisites and exact path/error return format, which are useful but not critical given the level of context shown.

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?

The description is a single dense sentence that earns its length: it covers request construction, response expectation, error rejection, disk persistence, return value, and relation to existing download flows. It is not fluffy, though the long dash-separated structure could be slightly easier to scan if split into separate sentences.

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 there is no output schema, the description appropriately states the return value ('devolve o caminho'). It also covers the main invocation-relevant behaviors: request construction, binary response expectation, and rejection of spoofed HTML errors. Some context is left implicit, such as requiring a prior login/session and the exact shape of the returned path, but the description is complete enough for an agent to select and invoke the tool safely.

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?

The input schema covers 100% of the parameters with descriptions, so the baseline is 3. The description adds only a general mapping to method, url, and form fields; details like 'application/x-www-form-urlencoded' and 'javax.faces.ViewState' are already present in the schema, so the description does not add meaningful parameter semantics beyond it.

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 states a specific verb and resource: it builds and triggers a request to sigs.ufrpe.br expecting a binary file, saves it to disk, and returns the path. It also differentiates itself from the sibling-specific download tools (sigaa_get_historico_pdf, sigaa_get_vinculo_pdf) by explicitly framing itself as the generalized download flow for any SIGAA download action.

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 gives clear context: use it when a SIGAA action is expected to return a binary file (PDF, schedule attachment) instead of HTML, and it generalizes hardcoded download flows for arbitrary actions. It does not explicitly name sibling tools or state when-not-to-use, so it stops short of full routing guidance.

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