gsc_list_sites

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

With no annotations, the description carries the entire behavioral burden, yet it discloses nothing beyond the bare operation. It does not say whether the list is scoped to the authenticated user's permissions, whether OAuth/credentials are required, whether results are paginated, or what a returned property looks like.

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 front-loaded sentence with no filler or redundancy. For a zero-argument listing tool this is an appropriately sized description.

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?

With no annotations, no output schema and no parameters, the description is the only source of information, and it omits what the call actually returns (property identifiers, permission levels, format) and any auth context. Adequate to identify the operation but not complete for calling it confidently.

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 the baseline of 4 applies; there is nothing for the description to disambiguate. The description correctly implies no filtering or input is 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?

States a specific verb ('Lista') and resource ('propiedades accesibles en Google Search Console'), which is enough to separate it from bing_list_sites by data source. It never explicitly names that sibling or scopes what a 'propiedad' contains, so it stops short of a fully discriminating 5.

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?

Usage is only implied: as a listing call it is the natural discovery step before gsc_search_performance, gsc_sitemaps or gsc_inspect_url, but the description says nothing about when to prefer it over bing_list_sites or that it should be called first. No exclusions or prerequisites are given.

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