List Search Console properties

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safe-read profile is covered. The description adds real value beyond that: it explains the two identifier forms, clarifies that sc-domain: spans all subdomains and protocols while URL-prefix matches exactly, and notes the permission level is returned.

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 tight sentences: purpose, identifier semantics, and the call-first instruction. The most actionable advice (call this first, pass the identifier) is front-loaded alongside the purpose, and every sentence earns its place.

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 zero-parameter, read-only listing tool with no output schema, the description covers what is returned (properties plus permission level) and the identifier formats an agent must understand to use the rest of the suite correctly. Nothing needed to invoke it correctly is 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 takes zero parameters, so there are no parameter semantics to document and the baseline is 4. The description's discussion of identifier forms concerns how the output is consumed by other tools, not this tool's inputs.

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 and resource (list Search Console properties) scoped to what the authenticated account can read, and adds the returned detail (permission level). The contrast with siblings is implicit but clear: this is the enumeration tool that feeds property identifiers to every other tool.

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?

Gives explicit sequencing guidance ('Call this first') and tells the agent what to do with the result ('pass the identifier verbatim as property to every other tool'). No exclusions are given, but there is no competing alternative for enumerating properties, so the guidance is effectively complete.

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