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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds specific behavioral detail beyond them: slug uniqueness conflicts and validation against published-site content queries that can reject a rename. It does not explain permissions or idempotence, but annotations cover the core mutation flags.

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 tight sentences, front-loaded with the mutable fields and constraints; the parenthetical limits and failure condition earn their place without padding.

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 destructive update with no output schema and low schema coverage, it supplies useful field semantics and slug failure modes. It still omits collectionId meaning and general error or permission context, keeping it 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 only 25%, so the description must compensate. It documents displayName length, description max/null-clear semantics, and slug conflict/published validation, but never describes the required collectionId parameter, and some details duplicate schema constraints.

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 gives a specific verb and resource and enumerates the mutable fields, so it is clearly an update rather than create/delete. It does not explicitly name sibling alternatives, but the purpose is otherwise unambiguous.

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?

Usage is only implied by 'Updates' and the field list; there is no explicit when-to-use/when-not-to-use guidance or comparison with sibling tools. An agent can infer this is for editing an existing collection, but must supply the context itself.

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