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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds value beyond them by previewing the returned content categories (stage, search, Bar, leads, pending human actions) — important given there is no output schema. The gain is muted because that preview is too cryptic to be reliably actionable.

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 id/no-id distinction, which is the right ordering. However, the compressed noun-list style ("Stage, search, Bar, leads and what needs the human") crosses from concise into ambiguous — a reader cannot reliably decode 'Bar' or 'leads' from the sentence alone.

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?

With no output schema, the description needs to carry the return-shape burden, and it only gestures at it with unexplained terms. Pagination and caching behavior are left entirely to the schema, which is acceptable given 100% coverage, but the missing plain-language account of what comes back leaves the agent guessing at the most complex part.

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%, so all four parameters are already documented with formats (cursor example, enum meanings, known_version caching). The description only restates the id/no-id split already present in the id field description and says nothing about cursor, status, or known_version. Baseline 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?

It states the resource and its dual mode ("Quest by id; no id: the list"), which an agent can act on, but the opening is verbless and telegraphic. The trailing phrase "Stage, search, Bar, leads and what needs the human" is internal jargon that doesn't resolve what the tool actually returns, and nothing separates it from siblings like operation_status or whats_new.

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 id-vs-no-id routing is stated, which is genuinely useful selection guidance for the two modes. There is no guidance on when to call this instead of operation_status, whats_new, or the sibling status tools, and no prerequisites or follow-up routing (e.g., to close_quest).

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