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

Goes well beyond the annotations: it discloses that both credentials are consumed, that no organization is ever created, how renaming/suffixing works, and what a repeated successful claim reports. This matches and enriches idempotentHint=true rather than contradicting it.

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 the core action, then rationale and edge cases. Dense and largely waste-free, though the site_token warning is repeated in the schema and slightly lengthens it.

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 token-claiming mutation with no output schema, the description covers prerequisites, credential consumption, naming behavior, and the repeat-call outcome. Nothing an agent needs to invoke it correctly is missing.

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 genuine meaning beyond the schema by explaining what site_token does instead and reiterating the claim_token requirement contextually. The new_name/org_name semantics are largely mirrored from the schema.

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?

Names a specific verb and resource ('Move a site published anonymously into one of the caller's Valet organizations, making it permanent'), and the contrast with publish_site/site_token distinguishes it from siblings. An agent can tell exactly what this does 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?

Explicitly states the credential to pass (claim_token, not site_token) and why, notes the prerequisite ('Requires connecting a Valet account'), and covers the repeat-claim case. It also rules out an alternative path (the site_token can never claim).

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