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

Annotations already establish readOnly/idempotent/openWorld, so the description's job is to add substance, which it does by disclosing the payload contents (permission level per property, brand-connection flag). With no output schema, this is the agent's only signal about what comes back, and it covers the essentials but not the shape or ordering of the response.

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 sentences: the first declares what is returned, the second declares the intended use. No filler, and the resource description is front-loaded before the routing hint.

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 zero-parameter, read-only lookup with no output schema, the description adequately covers both the return contents and the reason to call it. A brief note on response format (e.g. that each property includes its verification/permission status keys) would close the remaining 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?

The tool takes zero parameters, so there is nothing to document and the schema/description cannot conflict. Baseline for a parameterless tool.

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?

Names the specific resource (every Search Console property on the connected Google account) and states exactly what each entry carries: permission level and whether this brand is connected. This distinguishes it cleanly from data-reading siblings such as gsc_query and gsc_inspect_url.

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?

Explicitly tells the agent when to reach for it: to resolve the exact property string needed as the `site` argument by the other gsc_ tools. It sets up a clear prerequisite relationship, though it doesn't state any exclusions or conditions where it shouldn't be called.

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