Relatório de notas

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

With no annotations provided, the description carries the responsibility for disclosing behavior. It reveals a stateful dependency (valid ViewState) and provides the remediation step. This is a meaningful behavioral disclosure, though it does not mention output format or error behavior if the ViewState is invalid.

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 two sentences with no filler. The purpose is front-loaded, and the prerequisite is stated as a direct instruction. Every word 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 parameterless tool, the description covers what data is returned and the only prerequisite needed to invoke it. It does not describe the return format or pagination, but no output schema exists, and the simplicity of the tool makes this a minor gap.

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 for this dimension is 4. There is no parameter information to add, and the description correctly focuses on the prerequisite rather than parameter details.

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 exactly what the tool returns: grades from the current and previous semesters. It is clear and specific to the 'sigaa_get_notas' resource, but it does not explicitly name or distinguish itself from sibling tools like 'sigaa_get_historico_pdf' or 'sigaa_get_componente'.

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 usage context by explaining the ViewState prerequisite and telling the agent to call 'sigaa_main_data' first if needed. It does not discuss when to choose this tool over alternatives, but the sequencing guidance is actionable and directly supports correct invocation.

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