gsc_add_site

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

No annotations are provided, so the description must convey behavioral traits. It discloses that ownership verification is required separately, which is a useful behavioral constraint. However, it does not mention side effects, permissions, rate limits, or whether the operation is reversible, leaving some gaps.

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 a single efficient sentence. The [WRITE] prefix is a helpful structural cue. It is front-loaded with the action and constraint. Could be slightly improved by adding structure like bullet points for prerequisites, but it is concise.

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 simple tool with one required parameter, the description covers the core action and a key behavioral caveat (verification). No output schema exists, so the return value is not described, but for a creation tool, the lack of output specification is acceptable. The description is fairly complete given the tool's simplicity.

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% with the parameter 'siteUrl' having a description. The tool description adds no additional meaning beyond the schema; it only restates the schema's description. Baseline 3 is appropriate since schema already documents the parameter adequately.

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 verb 'add' and resource 'property to Search Console'. It also includes a [WRITE] tag to indicate the operation type. However, it doesn't specify what a 'property' means in this context or distinguish from siblings like gsc_submit_sitemap, though the sibling tools are different enough that the purpose is clear.

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 does not provide any guidance on when to use this tool vs alternatives. It mentions that ownership verification is separate, which is a prerequisite, but no explicit when-to-use or when-not-to-use context. This is a gap for an agent deciding between tools.

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