gsc_sites

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

With no annotations, the description correctly indicates this is a read-only list operation. It doesn't mention rate limits, auth needs, or whether 'verified' includes pending sites, but its simplicity is adequate for a list-all tool.

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 description is a single sentence that perfectly captures the tool's purpose without any superfluous words. It's front-loaded and efficient.

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?

Given zero parameters and an output schema, the description is complete. It tells the user exactly what the tool does, and the output schema handles return value documentation. No additional information is needed.

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 input schema has zero parameters, so there is no need for parameter documentation. The description correctly conveys that no arguments are needed, and schema coverage is 100% (since there are no parameters).

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 states the tool lists all verified sites in Google Search Console, which is specific and distinct from sibling tools like gsc_site_details or gsc_audit that operate on a single site or perform analysis.

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 when a user needs to discover which sites are accessible, but doesn't explicitly state when NOT to use it or provide comparisons to siblings. However, given the context of sibling names, it's clear this is an enumeration tool.

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