gsc_doctor

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

Annotations already mark it read-only and idempotent; the description adds what the report contains (auth mode, token expiry, property count, cache state, defaults) and promises secrets are masked. This gives the agent confidence about side effects and output contents. No contradiction with 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?

Two short sentences with the core purpose first, followed by valuable specifics. Every word earns its place; the 'Secrets are masked' note is important but not over-explained.

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 diagnostic tool with an output schema, the description explains when to call it and what information it will surface. It covers purpose, usage timing, and behavior without omitting anything the agent needs to invoke it correctly.

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 the schema carries no burden and the description doesn't need to explain parameter meanings. Per the baseline for zero-parameter tools, this is a 4.

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 ('Report') and resource (server configuration and Search Console connectivity). Clearly distinguishes from sibling tools that query search data. The 'Call this first' line reinforces its role as a diagnostic entry point.

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?

Explicitly instructs 'Call this first when something fails', which is a clear trigger condition. Also explains that it reveals defaults every other tool applies, so it is meant as a pre-flight check for subsequent calls. No exclusions are needed because it's unambiguously the diagnostic tool.

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