Get a Quera problem

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuine context beyond them: the statement is Markdown with LaTeX, and no write/submit action is available here, which prevents an agent from attempting a submission through this tool. It does not cover behavior on an invalid or missing id, which keeps it from a 5.

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?

Two short blocks: the payload enumeration is front-loaded, then a single line of routing and scope guidance. Every sentence carries information, with no restating of the name or title.

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 one-parameter read tool with full annotation coverage, the description supplies the one thing structured data lacks: no output schema exists, and the description compensates by enumerating the returned fields and their format. Required context for correct invocation is present.

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 the single parameter already documents itself as "Problem id from qr_problems, e.g. '589'". The description adds no additional syntax, format, or constraint meaning for the id, so this is the baseline 3 case where the schema does the 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?

States a specific verb and resource ("Get one Quera problem") and enumerates exactly what the record contains: statement in Markdown with LaTeX, limits, difficulty, tags, solve stats and languages. The singular "one" implicitly separates it from the sibling list tool qr_problems, so an agent can distinguish it without opening either schema.

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?

Gives explicit sequencing guidance ("Call after qr_problems"), which tells the agent where the id comes from and establishes the correct call order for a detail fetch. It also adds a scope exclusion ("Submitting solutions is not possible here"), but does not name what to use instead for solving, so it stops short of full alternative routing.

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