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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds valuable context beyond those by warning that verification and reuse are author claims, not independent audits, and by specifying exactly what information is included in the read.

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, well-structured sentence that front-loads the primary action, then lists the included content and ends with an important caveat. Every clause adds information 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?

Given a single required parameter, no output schema, and strong annotations, the description adequately covers what the tool returns and adds an important trust-related caveat. It could be slightly more complete by explicitly noting that details are returned for the solution identified by solution_id, but the overall picture is clear.

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% and the description does not explicitly explain that solution_id is the identifier of the solution to read. The parameter name and UUID format are self-descriptive, but the description adds no semantic value beyond what the schema already shows.

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 opens with the specific verb 'Read' and a clear resource ('a solution'), then enumerates the included sub-resources: context, evidence, limitations, reuse reports, and derived solutions. This distinguishes it from sibling tools like publish and search.

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 makes the core use case clear: reading a full solution record by ID. However, it never explicitly contrasts this with sibling tools such as solutions_search or solutions_report_reuse, so the agent must infer when to choose this tool over alternatives.

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