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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is partly covered. The description adds genuinely non-structured behavior: visibility changes only take effect 'the next time the site is published', which is important deferred-effect context an agent cannot get from schema or annotations. It stops short of stating auth/permission requirements or whether a visibility downgrade disrupts an already-live site.

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?

Three front-loaded sentences: the trigger and capabilities first, the publish-timing caveat second, the sibling redirect last. No filler, and the most decision-relevant information (what it does, when it applies) comes before the routing note.

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 explanation, and the description covers both mutations, the enum semantics, and the sibling boundary. Minor gaps remain: it does not say whether renaming affects the published URL/address (a natural confusion with set-site-address) or what permissions the caller needs.

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 only 50% (site_id and visibility lack descriptions), so the description must compensate — and it does by unpacking the three visibility modes and their meaning. The password constraint is echoed from the schema, adding little, and site_id remains unexplained, but the enum semantics are fully carried by the description.

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 names the two concrete mutations the tool performs: renaming a project and setting published-site visibility (public/password/private). It explicitly distinguishes itself from the sibling edit-site, which handles page titles, descriptions and SEO, so an agent can route correctly without opening either 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?

It gives an explicit trigger ('when the user wants to rename... or choose who can see the published site') and an explicit anti-trigger by redirecting SEO edits to edit-site. The password rule ('only send it when the user gives one') further scopes correct invocation.

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