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

Annotations already declare non-readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the rename propagates to three surfaces (switcher, header, SEO defaults) and is recorded in version history, implying recoverability. It stops short of stating required permissions or what happens to other name-derived fields.

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 short sentences, the primary effect front-loaded ahead of the disambiguation. Every clause carries information — what changes, that it is versioned, and which sibling to use instead.

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 3-parameter, non-destructive mutation with full schema descriptions, no output schema, and a rich annotation set, the description covers purpose, side-effect surfaces, reversibility, and alternatives. Only permission requirements and confirmation of what the call returns are absent, and the return side is partly excused by the lack of an output schema.

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%, so the baseline is 3, but the description adds real meaning by spelling out the blast radius of the single substantive parameter `name` — it drives the switcher entry, the site header, and SEO defaults, not just a display label. The optional `user_goal` parameter is covered by the schema and needs no further elaboration here.

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 a specific verb and resource ('Rename the site') and then scopes exactly what gets renamed: the site switcher label, the header, and the SEO defaults. It explicitly distinguishes itself from rename_page and update_site_settings, so an agent can route correctly without opening the 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 names two sibling alternatives with the precise condition that selects each: rename_page for a single page, update_site_settings for the browser-tab title. That is explicit when-to-use/when-not guidance rather than implied usage.

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