list_properties

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

With no annotations provided, the description carries the full burden. It discloses that the tool retrieves 'all verified sites, domain properties, and URL-prefix properties', indicating a read-only listing of accessible resources. However, it doesn't explicitly state behavior for empty accounts or permission issues, leaving a minor 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?

Three concise sentences front-loaded with the main action. Every sentence adds value: first states function, second adds detail on what is listed, third provides usage context. No unnecessary words.

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 zero parameters and the presence of an output schema, the description is complete. It explains what the tool returns (list of properties/sites) and when to use it (first step to get site_url). No further details are needed for a simple listing tool.

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?

There are zero parameters, so schema_description_coverage is 100%. The baseline for no parameters is 4, and the description does not need to add extra details since there is nothing to parameterize. It correctly omits any parameter references.

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?

Description clearly states it lists all GSC properties and sites the user has access to, with specific verb 'List' and resource 'properties and sites'. It distinguishes from sibling tools like add_site or get_site_details by focusing on enumeration rather than individual operations.

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?

Explicitly says 'Always call this first to get the exact site_url needed for other tools', providing clear when-to-use guidance and establishing it as a prerequisite. The context signals show no required parameters, reinforcing its role as an initial discovery tool.

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