create_site

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows it's a mutation but not destructive. The description adds useful context: return values include 'site row + install snippet + privacy_policy reminder + optional badge.' It doesn't mention what happens on duplicate domain, but overall adds value beyond annotations.

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?

The description is five sentences, each serving a distinct purpose: primary function, usage alternative, direct use case, framework selection, and return value. No wasted words.

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?

Given the tool has only 2 parameters, an output schema exists, and annotations are present, the description covers purpose, usage, return contents, and parameter guidance. A minor gap: it doesn't specify behavior for duplicate domains, but this is likely covered by error handling or 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 description coverage is 100% for both parameters. The description repeats the framework detection hint from the schema's framework description and adds 'Pass the framework matching the user's project' which adds negligible new information. Baseline 3 is appropriate as schema already documents parameters well.

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 clearly states the tool's purpose: 'Register a domain in Gizmo and return the install snippet.' It uses a specific verb ('register') and resource ('domain'), and distinguishes itself from sibling tool setup_analytics_for_site by explaining when to use each.

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 description provides explicit guidance: 'For first-time install asks... prefer setup_analytics_for_site' and 'Use create_site directly when the user only wants the site row created... or when integrating from another tool.' This clearly states when to use this tool vs the alternative.

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