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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered by structured data. The description goes further by enumerating what the returned entry contains (appearance, cause, who it hurts, fix, sources), which is real behavioral disclosure given the absence of an output schema.

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?

A single front-loaded sentence that establishes the verb, the key, and the return contents with no filler. Every clause earns its place by previewing the response shape.

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 must preview the return, and it does so adequately by listing the pattern entry's components. Minor gap: it doesn't say what happens when an unknown id is supplied, which would matter for error handling.

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 0% and the schema only says the id is a string, so the description carries the burden — it correctly explains that the parameter accepts either a short code ('a1') or a slug ('the-unchosen-gradient'). This is meaningful clarification beyond the bare string type.

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 and resource ('Get one full pattern entry by id or code') and the word 'one' implicitly separates it from list_patterns/search_patterns. It does not explicitly name the sibling tools, so an agent must still infer the boundary from the singular scope.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as search_patterns or list_patterns. The example identifiers hint that a known id is required, but nothing tells the agent when this tool is the right choice over its siblings.

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