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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds that results are paginated and limited to ids and summaries, but does not disclose ordering, filtering behavior, or pagination defaults, which are relevant beyond the annotations.

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 a single focused sentence with no wasted words. The key information—paginated, pattern ids and summaries, vendored corpus—is front-loaded and sufficient for a first-pass understanding.

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?

Basic invocation is clear, and the output schema plus annotations cover return shape and safety. However, the optional filtering parameters are left unexplained, and there is no guidance about pagination behavior or how this listing relates to the sibling search tool, leaving some gaps for an agent deciding how to query.

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%, so the description carries the burden of explaining parameters, but it only hints at limit/offset through 'paginated.' The area and provenance filters are not mentioned at all, and no additional meaning is added to the parameter names beyond what the schema already shows.

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 clearly states a specific action ('Paginated inventory') and a specific resource ('pattern ids and summaries from the vendored corpus'). This distinguishes it from siblings like get_pattern (single item), search_patterns (searching), and list_public_pages (public pages).

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 description conveys that this is the tool for enumerating all vendored corpus patterns, but it does not explicitly say when to prefer it over search_patterns or get_pattern. Usage context is implied by 'inventory' and 'paginated', but no alternative routing or exclusion conditions are stated.

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