Pathauto Pattern List

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

With no annotations, the description carries full burden and discloses a genuinely non-obvious behavior: the filter fields 400'd and a single filter silently returns the entire collection, forcing client-side narrowing. That silent-over-return warning is valuable and goes well beyond anything structured. It omits pagination behavior (page_limit/page_offset semantics), which keeps it from a 5.

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 one-line purpose is front-loaded and the caveat paragraph stays on topic. The second paragraph is dense and slightly repetitive in re-spelling `filter[entity_type]`/`filter[bundle]`, but every sentence earns its place by documenting a failure mode an agent would otherwise hit.

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?

An output schema exists, so return values need no prose, and the description covers the single biggest trap (filter behavior). Given no annotations and 0% schema coverage across four parameters, the missing pagination guidance and the unexplained page_limit/page_offset keep it slightly short of fully complete.

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 schema offers no help, and the description compensates meaningfully for entity_type and bundle by explaining the id encoding ({entity_type}--{bundle}) and the both-required filtering rule. page_limit and page_offset receive no explanation at all, so two of four parameters remain undocumented.

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?

Opens with a specific verb+resource: "List pathauto patterns." The name/title and first line make it unambiguous that this is a read-only listing tool, distinguishable from pathauto_pattern_get by the plural scope. It does not explicitly name or contrast the singular get/delete siblings, so it falls short of a 5.

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 gives real call-time guidance (both entity_type and bundle are required together to filter server-side; one alone silently returns everything), which is actionable. However, it never states when to reach for this tool over pathauto_pattern_get or pathauto_pattern_create, and gives no exclusions or sibling routing. Usage is implied rather than prescribed.

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