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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes beyond that with pricing semantics ('the most the call can cost is held first and you are charged for what it returns; a call that fails costs nothing'), which is genuinely useful behavioral context for a metered call. It stops short of describing rate limits or output shape.

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?

Front-loaded with the core purpose, followed by a compact enumeration of outputs and a pricing note. Two sentences, no filler, though the middle enumeration is somewhat dense.

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?

Return categories are described despite the absence of an output schema, and annotations cover the read-only/open-world profile, so the core is adequate. The uncovered gap is parameter meaning for the seven undocumented inputs, which leaves an agent guessing on geo, language, depth, and freshness controls.

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 only 13% (essentially just idempotency_key), and 8 parameters exist including non-obvious ones like gl, hl, depth, fresh, domain, and location. The description adds no meaning for any of these, so it does not compensate for the schema gap as required at low 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?

States a specific verb and resource ('Audit a company's SERP digital footprint') and enumerates the concrete output categories (owned properties, entity profiles, Maps locations, third-party mentions, PAA). This makes it distinguishable from generic siblings like google_serp or company_profile, though it never explicitly names which sibling to prefer for adjacent needs.

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 of scope implies when this tool is appropriate (a comprehensive company-level SERP audit), which offers implicit usage context. However, there is no explicit when-to-use/when-not statement and no routing to or away from alternatives such as google_serp or company_profile, leaving selection largely to inference.

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