edubase_post_exam_results_export

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

The description richly discloses behavior beyond annotations: the link is unauthenticated, single-use, expires in one hour, exports only visible examinees, honors exam export settings, and requires reporting permission. This goes well beyond the basic read/write hints and helps the agent anticipate side effects and access 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?

The description is compact and front-loaded, starting with the core purpose and then adding security, permission, and scoping constraints. Every sentence conveys meaningful operational information without unnecessary elaboration.

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?

Together with the highly descriptive input schema and the presence of an output schema, the description covers the important operational aspects: link lifetime, authentication, permissions, visibility scope, and relation to export settings. No critical missing context prevents correct invocation.

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% and every parameter, including nested properties and enums, has a detailed schema description. The main description adds high-level export context but does not need to explain individual parameters. The baseline of 3 applies because the schema already handles the heavy lifting.

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 action and resource: 'Generate a download link for the results of an exam.' It clearly conveys that this is an export operation producing a shareable link, which is distinct from sibling tools that fetch or manipulate exam/result data directly.

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 useful usage context: the link is unauthenticated and shareable, only visible examinees are included, and reporting permission is required. It does not explicitly name alternative sibling tools or state when not to use this export, but the context is clear enough for an agent to decide when this tool fits.

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