Add Site

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the key precondition of owner verification and the mutating nature of the operation, but it does not explain what happens if the property already exists or whether verification is automatic. Some behavioral ambiguity remains.

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 compact sentences deliver the purpose first and the prerequisite second, with no filler. This is an ideal size for a one-parameter tool.

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?

The combination of a fully documented single parameter, a stated output schema, and an explicit prerequisite is sufficient for an agent to invoke the tool correctly. Minor gaps around duplicate-site behavior are not material to initial selection and calling.

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%, and the single site_url parameter is already documented with an example in the input schema. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 action ('Add') and a concrete resource ('a new property to GSC'), which cleanly distinguishes add_site from delete_site, list_properties, and the analysis-oriented siblings. The prerequisite about owner verification adds useful specificity.

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 provides clear usage context: this is the tool for registering a new property, and it is only appropriate when the caller has site-owner verification. It does not explicitly name alternatives, but the single-purpose nature of the add action makes the intended invocation obvious alongside the sibling tools.

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