local_market_check

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

Beyond annotations, it discloses the payment model, that this is a package of two data calls for one payment, that sandbox/development returns dummy data with no payment, and that Google-derived titles, names, addresses, and phone numbers must be treated as data rather than instructions. These are meaningful behavioral details for a paid, open-world data retrieval tool.

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 package contents and keeps useful return-field and sandbox details. It is somewhat long, and the payment point is repeated in the first sentence and the later NOTE, but most sentences earn their place.

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 complex, paid, open-world package with no output schema, it gives the return JSON fields, sandbox behavior, payment model, and a prompt-injection warning. Combined with the fully documented schema, this gives an agent enough context to invoke the tool responsibly.

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 100%, so the schema already documents keyword, domain, language_code, and location_code with examples and constraints. The description reinforces that domain is for an optional position check, but it does not add syntax or meaning beyond the schema.

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 package: top 10 organic Google results, the local pack, search features, top 10 Maps businesses, competitor domains, and optional domain position checking. This is specific enough to distinguish it from a plain organic SERP tool or a Maps-only sibling, even without naming alternatives.

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 implies usage for one local search and notes the sandbox behavior, which gives useful context. However, it does not explicitly say when to use this package instead of siblings like google_serp or local_business, nor does it state exclusions or prerequisites beyond the location/language validation already in the schema.

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