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

Annotations already declare readOnly=false, destructive=true, and closed-world, but the description adds real value beyond them: partial-update semantics, null-clears-override behavior, and an explicit authorization requirement that READ_ONLY access is refused. It still does not explain what the destructive flag means in practice (e.g., whether passing an array replaces the existing list).

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 purpose lands in the first clause, followed by partial-update rules, the null rule, and then the permission caveat ordered by likely relevance. Every sentence carries information, though the null-override sentence duplicates what crawlMinDelayMs and crawlMaxConcurrency already state in the schema.

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?

An output schema exists, so return values need no explanation, and the mutation's safety profile is covered by annotations. Partial-update, null semantics, and permission requirements are all present. The remaining omission is collection-field semantics (whether arrays replace existing values) for a tool flagged destructive.

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 only 33%: the two crawl parameters are documented in the schema, while tags, siteUrl, sitemapUrls, and brandedKeywords are bare. The description compensates only by restating those field names in prose and adding omit/null semantics that the schema largely already covers, leaving replace-vs-merge behavior and per-field limits unexplained.

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?

States a specific verb ('Updates') and resource scope ('the GSC Wizard metadata for a property'), then enumerates the exact editable field groups: tags, branded keywords, sitemap URL list, and crawl speed. This field set is unique among siblings such as add_site, delete_site, and update_indexnow_settings, so an agent can route to it without opening another 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?

Gives concrete operating conditions: only supplied fields change, omitted fields stay, and null clears a crawl-rate override. It also states the access precondition for shared properties (FULL required, READ_ONLY refused). It never names an alternative tool (e.g., create_gsc_property for creating) or says when not to use it, so it stops short of a full 5.

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