datasets_google_map_item

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

Transparent about returning stored business, but no annotations exist. Description does not disclose error behavior (e.g., if place_id not found) or any other traits. Acceptable for a simple getter.

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?

Single sentence, 20 words. Front-loaded with verb and resource. No wasted words.

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?

Complete for a simple retrieval tool with one parameter. Mentions dataset constraint. Could add detail on return value when not found, but not essential.

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 100%. Description does not add meaning beyond schema: 'by Google place_id' is already in schema. No new information about parameter usage or format.

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?

Description clearly states verb 'Get', resource 'stored Google Maps business', and retrieval key 'place_id' from specific dataset. Differentiates from siblings like 'google_map_place' by emphasizing 'stored' and dataset enum.

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?

No explicit guidance on when to use vs alternatives (e.g., google_map_place for live data). The mention of 'stored' implies dataset-only, but no direct comparison or exclusion.

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