portal_exams

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

With no annotations, the description carries the behavioral burden. The verb 'Get' implies a read-only operation, and 'upcoming or past' discloses temporal scoping, but the description does not mention defaults, response shape, pagination, or portal-specific access considerations.

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 a single front-loaded sentence with no filler. Every word contributes to identifying the resource and the available temporal modes.

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 tool's low complexity — one optional enum parameter, no nested objects, no output schema, and no annotations — the description is minimally viable. Still, it leaves the default view behavior implicit and does not clarify how it relates to similar portal tools, so it is complete enough to invoke but not fully self-sufficient.

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 one enum parameter with no description coverage, so the description's 'upcoming or past' effectively adds a gloss for 'upcoming' and 'archive.' However, it does not explicitly tie the wording to the view parameter or state what happens when view is omitted, leaving the enum to do most of the semantic work.

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 the verb 'Get' and the resource 'exams and written tests,' making the tool's purpose clear. It does not explicitly contrast with sibling tools such as portal_evaluations, so there is some ambiguity about boundary between exams and evaluations.

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 phrase 'upcoming or past' implies when the tool is appropriate and maps naturally to the view parameter. However, it never says when to prefer this tool over sibling tools like portal_evaluations or portal_assignments, nor does it give exclusions.

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