List Search Console sites

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

With no annotations, the description carries full responsibility for behavioral disclosure. It adequately states the operation's outcome: listing all accessible properties and exposing permission levels. It does not mention potential side effects (none expected) or limitations like pagination, but for a simple list operation, this is sufficient transparency and does not hide any surprising behavior.

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, efficient sentence that front-loads the action and resource, then adds the key detail of permission levels. There is no fluff or redundant phrasing, making it easy for an agent to parse quickly.

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, no-output-schema tool, the description is complete. It tells the agent exactly what will be returned: all properties the service account can access, including permission levels. Nothing else is needed for correct invocation or interpretation of results.

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, so the schema is complete (100% coverage) and there is nothing for the description to add. The baseline for 0-parameter tools is 4 because the schema already defines everything. The description's mention of 'permission levels' does not pertain to parameters but to the output, so it doesn't add parameter semantics but is not 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 states a specific action ('List'), a clear resource ('all Google Search Console properties'), and the scope ('the service account has access to, including permission levels'). This precisely differentiates it from siblings like gsc_add_site or gsc_search_analytics, which operate on specific properties or metrics.

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 provides clear context about what the tool does and implies its use as an inventory/overview tool, distinct from the mutation-oriented siblings. However, it does not explicitly state when to prefer this over alternatives, nor does it mention exclusions like 'use this instead of gsc_list_sitemaps when you want sites only'. It stops short of explicit routing guidance.

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