list_sites

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing further — no indication of pagination, result ordering, or whether the returned properties are URLs vs. domain properties — but for a zero-argument read-only enumeration the behavioral surface is small, so this is not a severe gap.

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 the resource named first and the access scope immediately after. No filler, no redundancy against the title or annotations.

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 simple zero-param list tool with no output schema, the description is only minimally sufficient: it does not say the result is the set of site identifiers the other tools consume, nor whether the caller should expect a complete or paginated enumeration. An agent can call it confidently but cannot predict the shape of what comes back.

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 no parameters, so there is no parameter meaning to convey; baseline is 4 per the zero-parameter rule. The description correctly implies no filtering input is expected.

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 concrete verb and resource ("List Search Console properties") plus the scope qualifier "accessible to your account." No sibling tool (search_analytics, inspect_url, list_sitemaps, etc.) lists properties, so an agent can distinguish it from all of them without opening any schema.

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 gives no when-to-use guidance: it never says this is the discovery step that yields the site identifiers required by search_analytics or inspect_url, and it names no alternatives or exclusions. Usage is only inferable from the verb "List."

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