Pathauto Pattern Delete

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation deletes a pattern, which is a destructive action, but says nothing about permanent removal, required permissions, reversibility, or effects on generated URL aliases. For a mutation tool with zero annotation coverage, this is a significant gap.

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 front-loaded sentence with no wasted words. It is appropriately sized for a simple delete tool, though its brevity contributes to gaps in other dimensions rather than to structural weakness here.

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?

The tool is structurally simple: one required parameter and an output schema, so return values need not be described. However, with no annotations and 0% schema description coverage, the description should at least explain what pattern_id is and what deletion implies. It leaves an agent unable to call the tool confidently without first consulting sibling list/get tools.

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 has one required parameter, pattern_id, and schema description coverage is 0%. The description does not mention the parameter at all, so it does not explain whether pattern_id is a machine name, numeric ID, UUID, or another identifier. The description fails to compensate for the schema's lack of parameter documentation.

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: 'Delete a pathauto pattern.' This clearly identifies the action and object, and distinguishes it from sibling tools like pathauto_pattern_create and pathauto_pattern_update. It lacks any scope or sibling differentiation beyond the obvious action, so it is strong but not exceptional.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, whether the pattern must exist, whether the deletion is recoverable, or how it relates to sibling tools such as pathauto_pattern_list or pathauto_pattern_get. Usage is only implied by the verb.

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