wordpress_set_canonical_url

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

The description does not disclose any behavioral traits beyond the basic action. No annotations are provided, so the description carries full burden but fails to mention side effects (e.g., overwriting existing canonical URL), validation, or required permissions.

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 very concise at one sentence, but it is not front-loaded with key information and lacks any structure or additional context. It is succinct but overly minimal.

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?

Given the lack of output schema, low schema coverage, and many sibling tools, the description does not provide enough context for proper selection and invocation. Missing details on what 'set' entails (e.g., validation, overwrite behavior) and return value.

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 input schema has two required parameters with no descriptions. The description adds no additional meaning to the parameters, leaving their format, constraints, or source unclear.

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 the action (set) and the target (canonical URL for a post), making the purpose understandable. However, it does not differentiate from other similar 'set' tools on the same server, which could cause confusion.

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?

No instructions are provided on when to use this tool versus alternatives (e.g., set_seo_meta, set_og_tags). There is no mention of prerequisites or scenarios where this tool should or should not be used.

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