edubase_get_exam_results_raw

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds behavioral context by stating it returns raw answers, warns about additional permissions, and notes it is not user-facing.

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 concise with three succinct sentences. It front-loads the purpose, then provides a usage guideline and key behavioral detail. Every sentence adds value without redundancy.

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 the simple read-only operation with one parameter and an existing output schema, the description covers purpose, usage, return content, and permission context. It lacks details on result size or pagination, but is sufficient for the tool's complexity.

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 100% description coverage for the single 'exam' parameter ('exam identification string'). The description does not add further semantic meaning beyond that, but schema coverage is high, meeting the baseline.

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 tool's purpose: 'Get raw results for a specific exam.' It specifies the verb 'get' and the resource 'raw results', and distinguishes from sibling tools like 'edubase_get_exam_results_user' by emphasizing that this returns detailed raw data including all answers.

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 explicit usage guidance: 'Only use this if very detailed results are needed!' and 'It is not meant to be displayed to the user.' This directly informs the agent when to use this tool versus a simpler alternative.

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