list_sites

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context about permission levels and the exactness of the returned URLs, which is not captured in annotations, enhancing transparency without contradiction.

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 deliver the core purpose and essential usage context. The first sentence states the resource and scope, the second emphasizes the critical dependency on returned values. No fluff or redundancy.

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 the annotations and schema, the description is complete for an agent to call correctly. It clarifies the output format (siteUrl and permission) and the importance of exact values, covering all necessary aspects without needing an output schema.

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 single parameter (account) is fully described in the schema, including how to omit it and how to discover valid values via list_accounts. The description does not need to add more, as the schema provides complete semantic coverage.

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 it lists all Search Console properties accessible by the account, includes permission levels, and explicitly positions it as the starting point. It distinguishes itself from siblings like get_site and add_site by focusing on the complete enumeration and the necessity of using its returned siteUrl values.

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?

It explicitly says 'Start here' and explains that the returned siteUrl strings are required by other tools to avoid trailing-slash and sc-domain mismatches. This gives clear when-to-use guidance and highlights a critical dependency, making the usage context unambiguous.

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