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

Annotations already declare the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantive context beyond that: the connection prerequisite, the onboarding URL to fix a missing connection, and how the property is resolved when multiple Google accounts are linked. That auth/precondition behavior is exactly what annotations cannot convey.

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?

Four tight sentences, front-loaded with the action and then the return payload, prerequisites, and account resolution. Every sentence carries information; the return-field enumeration is justified because no output schema exists, though it is the one part that runs slightly long.

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?

With no output schema, the description compensates by enumerating the returned facets, and it covers the connection precondition and multi-account behavior for a read-only, open-world inspection tool. Nothing an agent needs in order to invoke it correctly is missing.

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% with only two parameters, so the schema already documents both 'url' and 'site' with examples. The description adds only an implicit note that the property is read through the account that can see it, which does not clarify parameter syntax or format beyond the schema. 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?

States a specific verb (Inspect) and resource (a specific URL's indexing status in Google Search), and enumerates the returned facets (indexed status, coverage state, last crawl, mobile usability, rich results). It is clearly distinguishable from the neighboring GSC analytics tools (top pages, queries, sitemaps) which do not perform per-URL inspection.

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 the operative context: it requires Google Search Console to be connected and points the user to rankparse.com/dashboard/integrations to connect it, plus the multi-account resolution rule. It does not explicitly contrast itself with siblings like get_gsc_properties (which one might need first to know valid site values) or state when not to use it, so it stops short of full when/when-not guidance.

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