searchconsole_discover

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

The description reveals an important behavioral trait: 'Operational searchconsole tools are hidden until discovered.' This adds value beyond the readOnlyHint annotation. It doesn't elaborate on return format or filtering, but the readOnly annotation already informs about side effects.

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 concise: it leads with purpose, adds a clear usage instruction, and lists the operations. The list is long but necessary for a discovery tool. No extraneous wording.

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 that this is a simple discovery tool with good annotations and full schema coverage, the description adequately explains the hidden-tools mechanism and what to do next. It doesn't mention the query filter, but that is covered by the schema.

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 input schema fully documents the only parameter 'query' with a description ('Keyword to filter the returned operations'). The tool description adds no additional semantics, so the baseline of 3 applies for high schema coverage.

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's purpose: 'List the available searchconsole operations.' It uses a specific verb (List) and resource (searchconsole operations), and it distinguishes from sibling discover tools by specifying searchconsole.

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 says 'call this first, then call the tool you need by name,' which clearly indicates when to use this tool and the workflow. It also provides the list of operations, making the next steps obvious.

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