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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds meaningful behavioral context beyond that. It warns that Google withholds low-volume queries, clarifies that absence of data must not be read as absence of demand, and explains the decision implications of each bucket.

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?

The description is dense but efficient: three sentences that front-load the core listing behavior, then add the decision-critical bucket definitions and the data caveat. Every sentence contributes information an agent needs for correct interpretation.

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?

With no output schema, the description adequately covers the return shape, including bucket, impression periods, clicks, position, and ranking page. It also covers the important caveat about missing query data, making it complete enough for an agent to invoke the tool and interpret results.

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?

Schema description coverage is 67%, with limit and bucket already well described in the schema. The description reinforces the bucket semantics but does not clarify workspaceId, which remains undocumented; it also adds no new parameter-level details beyond what the schema provides.

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 names a specific verb and resource: listing Search Console queries for the connected property, and it enumerates the returned fields (bucket, impressions, clicks, average position, ranking page). It is clearly differentiated from unrelated list tools by the gap-analysis bucket focus, though it does not explicitly name or contrast any sibling 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?

The description gives strong operational guidance for interpreting buckets, explaining which bucket justifies new content, which calls for editing an existing page, and which requires human triage. However, it does not explicitly state when to choose this tool over related Search Console siblings like search_console_get_demand or search_console_dead_pages.

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