google_maps_posts: 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. It states it is a 'paginated fetch' and describes the returned data, implying a read-only operation, but it does not explicitly say it has no side effects or mention any prerequisites (e.g., needing one of dataId/placeId). The GET verb in the title helps, but the description itself is not explicit.

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 concise, starting with the core purpose, then listing use cases. It is efficient and easy to parse, though it could be slightly more structured with parameter explanations.

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 with four optional parameters and no output schema. The description lists returned fields and mentions pagination, which covers most essentials. However, it lacks an explicit note that either dataId or placeId is required, and does not describe any rate limits or error conditions. Given the sibling context and schema coverage, it is sufficiently complete for basic invocation.

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 covers all four parameters with descriptions, so baseline is 3. The tool description adds context by mentioning 'language targeting' and 'nextPageToken pagination' and that it fetches by dataId or placeId, which helps clarify the parameter usage 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 clearly states the tool fetches Google Maps Posts (timeline-style updates) for a place, distinct from sibling tools for reviews, photos, and place details. It specifies the resource and action precisely.

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 explicit use cases (small-business intelligence, local-marketing monitoring, etc.) and mentions the pagination and targeting options. However, it does not explicitly state when to use this tool over siblings, though the purpose differentiation is fairly obvious.

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