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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the description's bar is lower. It still adds real value by disclosing that this edits a PUBLIC surface and overwrites the prior value, though it says nothing about auth requirements or error/rate-limit behavior.

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?

Front-loaded with a 'WRITE:' marker, then the changeable fields, the hard constraint, and the endpoint. Three sentences, zero filler, in priority order.

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?

Covers mutability, public exposure, destructive overwrite, and the state-change boundary — sufficient for a 5-param mutation tool with rich annotations. It stops short of any return-value or partial-failure behavior, and there is no output schema to cover that gap.

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 coverage is 100% and every parameter already carries a description (including the confirm safety gate), so the schema does the heavy lifting. The description only adds the implicit scoping that name/description are the sole mutable fields — a marginal gain over structured data.

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?

Specific verb+resource ('rename a component or change its description') with explicit scope ('PUBLIC status page'), and it names what it cannot do (change state). An agent can distinguish it from sorryapp_update_notice and sorryapp_create_component without opening a schema.

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?

States both when to use (renaming/describing a component) and when not to (state changes), and redirects the latter to the notice tools. The only softness is that 'the notice tools' is a family rather than a single named sibling, but the routing is unambiguous.

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