Baixar declaração de vínculo (PDF)

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the core behavior (downloading a PDF and saving it to disk) and the key precondition (valid ViewState). It does not describe error behavior or file output details, but for a zero-parameter download tool this is reasonably transparent.

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 with no filler. The main purpose and side effect are front-loaded, and the prerequisite is stated clearly in the second sentence. Every sentence earns its place.

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 simple zero-parameter tool without an output schema or annotations, the description covers the essential action and the most likely failure point (missing ViewState). It omits return value and file path details, but these are minor given the tool's simplicity.

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 tool has zero parameters, so the baseline is 4. The description adds useful context by mentioning ViewState as a required runtime state, even though it is not an input parameter.

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 clearly states the action ('Baixa' - downloads), the specific resource ('declaração de vínculo do aluno em PDF'), and the side effect ('salva em disco'). This is specific enough to distinguish it from siblings like sigaa_get_historico_pdf, which deals with a different document.

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 provides clear usage context by stating that a valid ViewState is required and explicitly instructs calling 'sigaa_main_data' first if one is not already available. It does not discuss alternatives or exclusions, but the prerequisite guidance is concrete and actionable.

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