gsc_list_sites

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

With no annotations, the description carries the burden of behavior disclosure. It mentions that results are scoped to the 'authenticated Google account,' which is a key behavioral trait. It does not elaborate on return format or edge cases, but for a simple list tool this is acceptable.

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, front-loaded with the action ('List all...'), and every word earns its place. No redundancy or padding.

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 list tool with no output schema and no annotations, the description fully covers the tool's purpose, scope, and usage context. It even clarifies the relationship to other gsc_* tools, making it a complete entry point.

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 has zero parameters and schema coverage is 100% (empty schema). Per guidelines, a baseline of 4 applies since there are no params to document. The description adds no parameter details, but none are needed.

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's purpose: 'List all Search Console sites/properties accessible to the authenticated Google account.' This is a specific verb+resource+scope, and it distinguishes itself from sibling gsc_* tools that operate on specific sites.

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 second sentence, 'Use this to discover Site URLs for use with other gsc_* tools,' provides explicit context for when to use this tool (as a discovery step before other tools). It does not list alternatives or exclusions, but there are no obvious competing tools for listing sites.

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