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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: a conditional second output item carrying a one-time use ticket and a one-line instruction, plus the follow-up flow via report_outcome after redemption.

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?

Front-loaded with what is returned, then the input form, then the conditional ticket behavior. Dense but purposeful; the semicolon-chained second sentence is slightly harder to parse than it needs to be, but no sentence is pure 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?

With one param, no output schema, and a non-obvious side effect, the description must carry the return shape and it does enumerate the page contents plus the conditional ticket item. It could be slightly clearer about the ticket's purpose and how report_outcome consumes it, but nothing essential for calling the tool is 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 coverage is 100% and the single param is already fully described in the schema ('A pattern identifier such as supervisor, or an alias such as orchestrator-worker'). The description's 'Accepts a pattern identifier or a known alias' largely restates the schema rather than adding format, resolution, or error semantics.

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+resource ('One pattern page') and enumerates the page's contents (definition, aliases, fit hypotheses, failure modes, sources, executability). It is clearly distinct from list_patterns and search, though it never explicitly separates itself from the sibling `fetch`, which could also retrieve a page.

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?

Usage is only implied: an agent can infer this is a single-item lookup by identifier or alias versus listing/searching. There is no explicit 'use this when...' guidance, and no statement of when to prefer report_outcome or fetch instead.

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