gsc_site_get

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

With no annotations, the description carries full burden. It explicitly states a read operation ('get'), which is safe and idempotent, but does not disclose error behavior, rate limits, or idempotency beyond the verb. For a simple GET tool, this is adequate but minimal.

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?

A single sentence that front-loads the purpose ('Search Console: get one property and the user's permission level'). Every word earns its place; no wasted content.

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?

The description covers the basic purpose but omits details about response structure (no output schema) and error handling. For a one-parameter GET tool, it is adequately complete but could be more informative, e.g., mentioning that the response includes the site object and permission level.

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%, and the description repeats the schema's parameter description verbatim ('Property URL exactly as in Search Console, e.g. https://example.com/ or sc-domain:example.com'). No additional semantic enrichment is provided.

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 identifies a specific verb ('get') and resource ('one property and the user's permission level'), distinguishing it from sibling tools like gsc_site_add (create) and gsc_sites_get (list).

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 implies usage for retrieving a single site's details and permissions, but does not explicitly state when to use this versus gsc_sites_get or other tools. No exclusions or alternative guidance provided.

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