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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real behavioural substance beyond that: the edition/mark model, that absent 'readAt' means not yet read, and crucially that 'people' and 'earlier' only appear for the project lead — a permission-dependent output shape an agent must know. It does not cover error behaviour for a missing page id or any size/pagination concerns.

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 content is dense with no filler, but it is delivered as one long run-on paragraph with awkward clauses ('whether somebody is asked to read it and mark so', 'and 'earlier', the marks on earlier editions'). Field semantics would read far better as a short list, and the lead-only extras are buried mid-sentence.

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 must explain the return shape and largely does: edition resolution, required/readAt, the three forms of 'readers', and the lead-only 'people'/'earlier' blocks. Missing only edge behaviour (nonexistent page, pages with no reading request beyond the null-edition hint).

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?

There is a single required parameter with 100% schema description coverage ('Page id (as returned by search_wiki).'), so the schema already does the work. The description adds no additional meaning about the id, which is the expected baseline-3 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 makes clear the resource is a wiki page's required-reading state ('whether somebody is asked to read it and mark so'), and it explicitly cross-references get_wiki_page_approval for the approved edition, separating it from the approval sibling. It lacks a clean leading verb (it opens with a noun phrase, 'A wiki page as REQUIRED READING'), so the purpose is clear but not maximally crisp.

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?

Usage is only implied: an agent can infer it should call this to learn who has been asked to read a page and who has marked it, and the pointer to get_wiki_page_approval helps resolve the edition field. There is no explicit statement of when to use this instead of get_wiki_page, mark_wiki_page_read, or set_wiki_page_readers, and no exclusions.

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