List Search Console properties

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

Annotations already declare readOnly, idempotent, and non-destructive behaviorched. The description adds value beyond that by mentioning the returned permission level and warning that URL format matters. However, it omits that the limit parameter defaults to 25, which can contradict 'Lists every' when a user has more properties.

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 compact, information-dense sentences. The first states the core action, the second gives crucial usage guidance, and the third reinforces safety. No unnecessary fluff beyond a brief 'Read-only' that is already in 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 one-parameter tool, the description is largely complete: it states the output includes permission levels and explains why the siteUrl format matters. A small gap is that it does not disclose the default 25-row limit or possible pagination, which is relevant to the 'Lists every' claim.

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 limit is fully documented in the schema, including its default and rationale, so the description does not need to repeat it. The description adds no additional parameter meaning, making the baseline 3 appropriate.

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 the tool lists every accessible Search Console property with permission level. It even highlights the significance of the exact siteUrl format, distinguishing this discovery/list tool from other GSC tools like search queries, sitemaps, and 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 explicitly advises using this tool FIRST to retrieve the exact siteUrl string needed by other Search Console toolsikuha. It does not name a direct alternative or when-not-to-use, but for a site-list discovery tool, this is strong contextual guidance.

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