Atestado de matrícula (estruturado)

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

No annotations are provided, so the description carries the full burden. It discloses an important behavioral dependency (valid ViewState) and how to satisfy it. However, it does not explicitly state that the operation is read-only, nor does it mention failure behavior, so a 5 is not warranted.

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 no filler: the first front-loads what the tool returns, and the second provides the only necessary usage condition. 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 no-parameter tool with no annotations and no output schema, the description covers the key output content and the required prerequisite clearly. It does not describe the exact response structure or edge cases, but for invocation purposes it is sufficiently complete.

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 has zero parameters, so the rubric baseline is 4. The description correctly avoids inventing parameter details and instead focuses on prerequisite context.

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 identifies the resource (atestado de matrícula) and the data it returns: período letivo, vínculo, curso, and turmas matriculadas. The title adds 'estruturado', which distinguishes it from HTML/PDF siblings, but the first sentence lacks an active main verb and relies on the participle 'extraídos', so it is not a full 5.

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 explicitly states a required precondition: a valid ViewState. It also tells the agent exactly what to do if that precondition is not met: call 'sigaa_main_data' before. This is clear when-not and sequencing guidance.

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