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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, but the description adds value beyond that: it emphasizes the operation is private, mentions the optional cursor for later feedback, and warns that returned text is untrusted participant data. No contradiction with 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, zero redundancy. The main purpose is front-loaded, followed by usage and a security note. Every clause earns its place, with no 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 read-only, idempotent tool with rich annotations, the description covers purpose, usage, pagination, and security. No output schema exists, but the warning about untrusted data and the explicit lack of side effects make it sufficient for an agent to call it correctly.

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%, yet the description explains both parameters: 'participant_token' as your existing private token, and 'after' as an optional cursor for later feedback. This provides meaning beyond the schema's patterns, fully compensating for the coverage gap.

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 clear verb (read) and resource (reuse reports and adaptations of your solutions), and explicitly lists what it does not do (register, publish, mark read, require polling), which distinguishes it from the siblings solutions_publish, solutions_report_reuse, and solutions_read.

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 provides explicit usage instructions: send your existing participant_token and optionally use the 'after' cursor for pagination. It also states exclusions ('Does not register, publish, mark read or require polling'), making clear when not to use this tool and implying alternatives for those actions.

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