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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral information: it discloses the response contents (correct option, a one-line rule note, and a theory section), which is valuable given there is no output schema.

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?

It is short and front-loads the return fields, but the colon-list fragment lacks a subject and verb, which makes the first read ambiguous. One rewrite into an action statement would cost nothing and remove the ambiguity.

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 simple 3-parameter read tool with full schema coverage and annotations, this is close to adequate; describing return values compensates for the missing output schema. It still omits when to prefer it over siblings and what happens on an unknown question_id.

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%, with enums documented for lang and option and an example id (bs-001) for question_id. The description adds no further meaning about parameters, so the baseline of 3 applies.

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 is a sentence fragment that lists outputs (right option, one-line rule note, theory section) rather than stating a verb+resource action like 'checks whether the chosen option is correct.' An agent can infer the purpose, but there is no differentiation from siblings like explain_question or grade_exam, which plausibly overlap.

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 guidance on when to use this versus explain_question (which likely explains a question) or grade_exam (which likely grades a set). No prerequisites, no exclusions, no conditions are given.

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