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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description adds only that entries carry example counts, which is useful but largely duplicated by the output schema. A 3 is appropriate given the low marginal value over structured fields.

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?

Two front-loaded sentences that name the resource first and the intended follow-up second, with no padding. The 'Example: {}' fragment is slightly awkward and marginally redundant with the empty schema, keeping it from a 5.

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 no-argument listing tool with a full output schema and complete annotation coverage, the description supplies everything needed: what is listed, what each entry carries, and what to do next. Return-format details are correctly left to the output schema.

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?

The tool takes zero parameters, so the baseline is 4. The trailing 'Example: {}' correctly signals an empty argument object, reinforcing what the empty schema already says; there are no parameters whose meaning needs further explanation.

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 ('Every UI and interaction pattern resources are filed under') and enumerates concrete members (Command Menu, Onboarding, Empty State), so an agent knows exactly what taxonomy it is enumerating. It also names the sibling it feeds into (get_pattern), separating it from browse_vertical and the list_people/list_resources family.

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?

'Use it to pick a slug for get_pattern' gives an explicit follow-up condition that selects this tool over its siblings. It stops short of stating when NOT to use it (e.g. when you already have a slug and should call get_pattern directly), so it is clear context without full exclusions.

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