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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true, openWorldHint=false), so the description only needs to add blast-radius context — and it does, by defining exactly what is and is not affected by the rename. It does not address permissions, reversibility, or error behavior, which leaves some behavioral ground uncovered given destructiveHint=true.

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 action front-loaded and the constraint immediately after. Every clause carries information; nothing is redundant with the title or schema.

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 two-parameter mutation with no output schema and annotations already covering the safety profile, the description supplies the one thing an agent most needs — the scope of the change. Minor gaps remain: how the siteId is obtained, and whether omitting the optional 'name' makes the call a no-op.

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 0%, so the description carries the burden; it maps conceptually to the 'name' parameter (the display name) but never names or explains it, and says nothing about 'siteId' (UUID of the site to rename). It also does not clarify that 'name' is optional while 'siteId' is required, which is a non-obvious schema fact.

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?

States a specific verb (Rename) and resource (a Replo site's dashboard display name), and immediately scopes it against the adjacent concerns that similar-named siblings (update_site_metadata, update_site_navigation, update_site_tracking, publish_site) would otherwise be confused with. An agent can tell this is the display-name-only mutation without opening any 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?

The second sentence gives a clear negative boundary (not the SEO page title, not published page content), which steers the agent away from using this for metadata or content edits. It stops short of naming the alternative tool (update_site_metadata) explicitly or stating any prerequisite, so it is strong context rather than a full when/when-not rule set.

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