Add Website

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

Annotations already declare this a non-read-only, idempotent, non-destructive, open-world operation, so the description's remaining job is small. It does add genuinely useful context beyond them: the WSP_ALLOW_WRITES=true feature gate, which the agent needs to know before calling. It doesn't mention ownership verification or what comes back, which keeps it from a 5.

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 with no filler; the action comes first and the constraint follows. It is appropriately sized for a one-parameter tool, though the header largely restates the title.

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 single-parameter mutation with a fully documented schema and no output schema, the description covers the core mechanics and the write gate. It omits what happens after the property is added (verification requirement) and any note that results are visible via wsp_list_websites_gsc, leaving a modest gap.

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% and the single parameter's description already spells out exact-match URL forms and the sc-domain: prefix. The tool description adds nothing about which form to choose, so the baseline 3 applies.

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 states a specific verb and resource: 'Add a property to Search Console.' 'Property' distinguishes it from the sitemap-oriented siblings such as wsp_add_sitemap_gsc, though it never names those siblings explicitly.

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 gives a real prerequisite ('Requires WSP_ALLOW_WRITES=true'), which tells the agent when the call will succeed, but it offers no guidance on when to use this versus related operations like wsp_list_websites_gsc or wsp_show_website_gsc, and no note about when not to use it.

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