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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful behavioral context beyond annotations: OMARCHY-03 is free, four other cases require x402 payment, and cached replay fails closed requiring manual support.

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 very short and front-loads the single-case scope. It uses fragmentary sentences, but every clause carries some information and there is 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 one-parameter lookup tool with no output schema, the description omits what is returned, the meaning and format of case_id, and how to handle the four paid cases. It gives some payment and failure-mode context but leaves core invocation details missing.

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% for the required case_id parameter (string, maxLength 100). The description mentions 'OMARCHY-03' and 'four other cases,' which hints at valid values, but it never names or explains the case_id parameter, its format, or how to supply it.

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 says 'One approved case' but never states a verb like retrieve/fetch nor explains what an 'experience case' is; it only weakly implies the tool returns a single case. It does not differentiate from sibling list_experience_previews.

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?

No when-to-use guidance is provided, and the sibling list_experience_previews is not mentioned as a prerequisite or alternative. The payment notes describe cost conditions rather than when an agent should select this tool.

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