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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns 'immutable payment terms,' which is a useful behavioral detail beyond the schema. However, it doesn't disclose anything about error behavior, existence checks, or what happens if the room doesn't exist.

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?

A single sentence that is front-loaded with the verb and resource, and lists the specific fields returned. Every word earns its place; no filler or repetition.

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 simple read tool with one parameter and strong annotations (readOnly, idempotent, non-destructive), the description is nearly complete. It could mention what happens if the room doesn't exist or whether the name is case-sensitive, but the schema pattern already constrains the input. The lack of an output schema is mitigated by the description listing the returned fields.

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 0%, so the description must compensate for the single parameter 'name'. The description implies the name identifies the room but doesn't explicitly state that the 'name' parameter is the room name or explain the naming pattern. However, with only one parameter and a clear pattern in the schema, the meaning is fairly inferable. Baseline 3 is appropriate.

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 ('Read') and resource ('room'), and lists the specific fields returned: description, creator, visibility, and immutable payment terms. This clearly distinguishes it from sibling tools like list_rooms or find_rooms, though it doesn't explicitly name a sibling.

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 description implies this is the tool to use when you need a single room's details, as opposed to listing or searching rooms. However, it doesn't explicitly state when to use it versus alternatives like list_rooms or find_rooms, nor does it mention any exclusions or prerequisites.

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