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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the return shape (per-post title, description, image, posted_at, link, source/business name) in the absence of an output schema, and noting the dataId/placeId input flexibility, though it omits pagination or rate-limit behavior.

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 sentences, front-loaded with the core action and followed by the return fields and use cases. The use-case list is somewhat padded but each clause remains relevant; no significant waste.

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?

With no output schema, the description compensates by naming the per-post return fields, and it clarifies the input identifiers and language targeting. Complete enough for an agent to invoke it correctly, missing only finer operational details like limits or pagination.

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 all three parameters (hl, dataId, placeId) are already documented in the schema, including the 'either dataId or placeId' rule. The description merely restates 'by dataId or placeId, with language targeting' and adds no syntax or format detail, matching the baseline of 3.

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 uses a specific verb (Fetches) plus the resource (Google Maps Posts) and even enumerates the content type (offers, events, announcements, notices) fetched by dataId or placeId. It is clear enough to distinguish from most siblings, though it never explicitly contrasts itself with near-namesakes like google_maps_reviews or google_maps_place.

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 gives intended scenarios ('small-business intelligence, local-marketing monitoring, competitor activity tracking'), which is genuine when-to-use guidance. However, it offers no exclusions and does not route the agent to an alternative (e.g., reviews tool for reviews), so the guidance remains implied rather than decisive.

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