gsc_get_manual_operator_checklist

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

Description explicitly states the tool is read-only, never calls Google APIs, never requires credentials, and never mutates Search Console. This fully discloses its behavioral traits, especially since annotations are absent.

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-sentence description is extremely concise, front-loaded with the primary purpose, and each sentence adds unique value. No wasted words.

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?

The description covers purpose and behavior well, and an output schema exists (as per context signals) to detail return values. However, the lack of parameter explanation is a significant gap, making the tool's interface unclear for the agent.

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?

Input schema has two parameters ('focus' with default 'weekly', 'site_url' with default '') with no schema descriptions. The description does not explain what these parameters do or how they affect the checklist, leaving the agent with no guidance despite 0% 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?

Description clearly states the tool returns a stable read-only checklist for Search Console UI-only/manual surfaces. It specifies verb, resource, and distinguishes from sibling tools by noting it never calls Google APIs, requires no credentials, and never mutates Search Console.

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?

Description implies usage context: when an operator needs a checklist for manual review surfaces. It does not explicitly state when not to use it or list alternatives, but the sibling tools (e.g., get_search_analytics) suggest when API-calling tools are more appropriate.

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