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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds context they don't carry: the exact shape of the response (code, id, name, one-liner), which is valuable since no output schema exists.

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?

One front-loaded sentence that names the resource and the return fields with no filler or repetition of the title.

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 usefully communicates what comes back, and annotations cover the safety profile. The only omission is any mention of the optional track filter or how results are ordered or paginated.

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 100%, so the single 'track' enum parameter is already documented by the schema and the baseline is 3. The description does not mention the filter at all and its 'whole taxonomy' phrasing arguably understates the filtered mode, but it does not contradict the schema.

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 ('List') and resource ('the whole Slop Patterns taxonomy') and even enumerates the returned fields (code, id, name, one-liner). It distinguishes itself implicitly from search_patterns/get_pattern by emphasizing the complete enumerations, but never names those siblings explicitly.

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 word 'whole' implies this is the tool to use when you want the entire taxonomy rather than a targeted lookup, giving mild implied guidance. However, no alternatives are named and no when/when-not conditions are stated, so an agent must infer the distinction from sibling names.

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