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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond them: it discloses that inactive content is returned under a flag but must not be used for generation, a caveat an agent could not infer from the schema or annotations.

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, front-loaded with the core action before the flag guidance, and nothing is padding. Minor grammar slip ('a experience') and no wasted clauses.

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 does state what comes back (evidence and versions) and flags the inactive-content caveat. It is nearly sufficient for a two-parameter read tool; only the relationship to list_experiences is left implicit.

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 only 50% – include_inactive has no schema description – and the description compensates by explaining exactly what that flag does and when to set it. The experience_id constraint is carried by the schema, so this is a net-positive contribution rather than a repeat.

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 ('Read') and resource ('experience') and names what the payload contains ('evidence and versions'), which distinguishes it from list_experiences and the memory/timeline readers. However it never explicitly contrasts itself with the nearest sibling list_experiences, so it stops short of full sibling differentiation.

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 usage condition: set include_inactive=true when a review bundle is wanted, plus the constraint that inactive content must not be used for generation. It does not state when to prefer this over list_experiences or review_experience, so it is clear context without exclusions.

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