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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that searches are run both as typed and as a username and merged, lists the main returned fields, and states the $0.05 USDC cost via x402 when no API key is used. It does not explain pagination, error behavior, or authentication details with an API key, but it adds meaningful behavioral context.

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 front-loads the purpose and returned data, then adds the location-pinning hint and pricing in short follow-up sentences. It is compact and mostly well structured, though the phrase "searched as typed and as a username and merged" is slightly awkward.

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 single-parameter paid lookup with no output schema, the description provides enough context: what is searched, how to pin a location, what fields are returned, and the cost model. Minor missing details such as authentication with an API key or response shape are not critical for a basic call.

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 schema already documents the single query parameter with an example, and the description adds important query semantics by explaining the optional " near <place>" syntax and that the input is searched both literally and as a username before merging results.

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 clearly states that the tool finds Google Maps places tied to a person or business name/username and lists returned fields such as address, phone, coordinates, place ID, and Maps link. It is specific about the resource, though it does not explicitly differentiate this tool from nearby sibling lookup tools.

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 gives one useful usage hint: adding " near <place>" to pin a location. However, it does not explain when to use this tool instead of alternatives like facebook_name_search, instagram_name_search, or username_scanner, leaving the selection context implied.

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