google_maps_place: GET /

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

No annotations are provided, so the description carries the full burden. 'Fetches' implies a safe read operation, and the 17-field return list discloses what the agent gets. But it does not mention rate limits, auth requirements, error conditions, or pagination behavior — gaps for a no-annotation tool, though acceptable for a straightforward GET.

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 dense sentences plus a use-case list, with the purpose front-loaded and the return payload enumerated compactly. The use-case list is slightly redundant with the resource description but earns its place as routing signal. No filler or repetition.

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?

Moderate complexity (3 params, 1 required) with no output schema, so the description rightly compensates by enumerating the full return fields. The placeId source is covered by the schema. Missing only edge details like limits or error handling, which are minor for a details-fetch tool.

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 coverage is 100%, so the schema already documents all three parameters. The description adds only minimal meaning via 'optional domain/language localization,' which loosely maps to hl and domain. The schema itself already notes language-code and Google-domain constraints with allowed values, so the description adds little beyond baseline.

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 verb (Fetches) and resource (full Google Maps place data by placeId), then enumerates the return fields explicitly. It clearly distinguishes itself from the sibling tools (search, reviews, photos, posts) by being the single place-details endpoint.

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?

Provides clear use cases (local SEO audits, POI enrichment, lead generation, competitor mapping, location-aware agents) and the 'by placeId' phrasing implies it should follow a search that yields an ID. However, it does not explicitly name alternatives or state when not to use it, leaving sibling differentiation to inference.

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