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

The annotation readOnlyHint=true already covers the read-only nature, so the bar is lower. The description adds useful context by noting the result includes the experiences that answer the target experience, which goes beyond the schema. However, it doesn't disclose any error behavior, permissions, or other behavioral traits.

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 description is a single, front-loaded sentence with no unnecessary words. It efficiently conveys the tool's main output without repetition or 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?

For a simple read tool with one parameter, the description broadly explains the return value (full text plus answering experiences). However, with no output schema, it lacks specifics about the response structure, data types, error conditions, or pagination if any. Adequate but with notable gaps.

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 undocumented id parameter. It vaguely implies that id selects which experience by saying 'one experience', but it does not explicitly define id as the experience's unique identifier, nor does it specify expected values or format. Minimal compensation for a fully undocumented parameter.

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 clearly states the resource (an experience) and what is returned (full text plus answering experiences). The verb is provided by the title 'Read an experience', and the content implicitly distinguishes it from search_experiences and list_topics, though it does not explicitly name them.

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?

There is no guidance on when to use this tool versus alternatives. It does not state that the id parameter is required or that this tool should be used when you already know the specific experience ID, nor does it mention when to prefer search_experiences or list_topics. The only hint is the required id in the schema.

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