List Search Console properties

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable context beyond annotations by specifying the identity used for authorization and noting that exact property identifiers and permission levels are preserved in the output.

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 that begins with 'Read-only' and communicates scope, identity, and output fidelity without wasted 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 no parameters, a rich annotation set, and an output schema, the description covers all necessary context: read-only behavior, identity scope, result scope, and permission-level preservation. No critical information appears missing.

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 there is nothing to clarify beyond the schema. The description appropriately focuses on scope and output behavior rather than inventing parameter details.

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 uses a specific verb ('List') with a clear resource ('every Google Search Console property') and scope ('available to the current ADC identity'). It clearly distinguishes itself from siblings like query_search_analytics and inspect_url by focusing on property inventory rather than analytics or URL inspection.

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 conveys the appropriate context for use: enumerating all accessible properties for the current identity. It does not explicitly mention alternatives or exclusions, but the distinct purpose compared to sibling tools makes the usage context clear enough.

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