searchconsole_discover

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context by stating that it reveals hidden tools and by enumerating the available operations, which helps the agent understand the effect and scope of the call beyond the safety annotations.

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 front-loaded with the core action and sequencing instruction, then supplies the operation list compactly. The list is long, but every item is useful for understanding what the tool reveals, and there is no redundant prose.

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 discovery tool with no output schema, the description gives an adequate sense of what is returned: a catalog and hidden tools, including the named operations. Combined with annotations covering safety, this is nearly complete, though it could clarify how to invoke the revealed operations by name.

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 has 100% description coverage, and the single parameter is documented there as a 'Filter keyword.' The description does not add any additional meaning about the query parameter, so the baseline of 3 is 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 states a specific verb and resource ('Discover searchconsole'), explains that it lists a catalog and reveals hidden tools, and identifies itself as the required first call. It clearly differentiates itself from sibling discovery tools such as gmail_discover and drive_discover by naming the searchconsole domain.

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?

It gives explicit sequencing guidance: 'call first, then call the tool by name.' This tells the agent when to use it relative to the hidden tools it reveals. It does not compare itself to discover_all or explain when not to use it, so it falls just short of full alternative coverage.

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