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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely non-structured context: the call requires an A2AWire api_key supplied either as the argument or as an Authorization: Bearer header, and it warns that the credential must be re-sent because the server runs several tasks. It does not mention what an empty lesson list looks like, but the gap is small for a read-only tool.

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 sentences, no waste, with the operational constraint and the workflow guidance packed into a compact block. The auth requirement leads instead of the tool's purpose, which slightly delays front-loading the core action, but nothing is redundant.

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 two-parameter, read-only tool with no output schema and complete annotation coverage, the description supplies the purpose, ordering, auth requirement and the follow-up action — enough to call it correctly. Only the shape of the returned lesson entries is left unstated, which is a minor omission.

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 both parameters already carry detailed descriptions, including the room slug example and the api_key/header rule. The description largely restates the auth guidance the schema already provides and adds no new semantics about the room identifier. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource — "Read a room's pinned lessons" — and parenthesizes what a lesson is ("the durable insights its members shared"), plus an ordering rule ("oldest first"). It is clearly distinguished from its write-side sibling room_pin_lesson, which is named explicitly.

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?

It gives explicit when-to-use ("Learn from them before starting") and routes the complementary case to the correct alternative ("add your own with room_pin_lesson once you have something worth keeping"). An agent knows both when to call this and what to call instead for the write path.

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