read_current_exam_question

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: not that this is a read-only/side-effect-free call, not what the 'content-bound token' is for (presumably an anti-tamper binding used when submitting an answer), not what happens if no exam tab is present, and not whether the read advances any state.

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?

A single tight sentence with no filler. It is appropriately short, though the brevity comes at the cost of the details scored low above rather than through deliberate compression.

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?

An output schema exists, so return shape need not be explained, but the tool still leaves out the run_id contract, the meaning/purpose of the token, and the tab-state assumption — all things an agent needs to invoke it correctly in a long orchestration workflow.

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 0% for the single parameter run_id, so the description must compensate and it does not — run_id's format, provenance, and whether it must match an active run are all left unexplained. With an undocumented required parameter on a state-sensitive tool, this is a real gap rather than a baseline case.

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 gives a specific verb and resource ("Read structured question/options and a content-bound token") plus a locator ("the existing tab"), so the operation is identifiable. However, the sibling list contains several near-identically named tools (read_owned_exam_question, read_owned_exam_observation, preview_owned_exam_questions, inspect_exam_page), and nothing here distinguishes this one from them.

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?

There is no statement of when to call this versus the many sibling readers, nor of prerequisites. "The existing tab" faintly implies an already-open exam tab, but the agent is left to infer that a tab must exist, be the right tab, and be in the right state.

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