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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description goes beyond them by disclosing the actual content shape of the response, including the odd but important detail that challenges are questions only with answers 'earned by looking', and that credit must be cited. It does not mention that visitor notes exist or are off by default, though the schema does.

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?

Front-loaded with the verb and resource in the first four words, then a compact enumeration of returned content. The single long sentence is dense but each clause carries distinct information; the parenthetical about citing credit and question-only challenges is high-value, not filler.

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?

There is no output schema, so the description carries the return-value burden, and it does so thoroughly by naming each section of the piece record. The only real omission is that it never mentions the optional visitor-notes payload or the visitor-name identity model, both of which the schema covers on its own.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the piece_id must come from a room's route, implying ids are route-derived rather than free-form slugs. Nothing is added about room_id, visitor_name or include_visitor_notes beyond the already-rich schema text.

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 ('Read one piece in full') and then enumerates the payload: title, author, date, license/credit, bilingual description, context, how-to-look, curious fact, guide voices, challenges. That enumeration cleanly separates it from search_pieces (discovery), get_room (containers) and piece_of_the_day (editorial pick).

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 a concrete precondition for the required id ('Use an id from a room's route'), which tells the agent to come here after navigating a room rather than starting here. It stops short of naming the alternatives it is not (search_pieces, recommend_piece, piece_of_the_day) or stating exclusions, so it is clear context without explicit routing rules.

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