datasets_google_map_item

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

No annotations provided, so description holds burden. Discloses null rating and geo for service-area businesses, and dataset enum value. However, does not mention idempotency, authentication needs, or read-only nature.

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?

Four sentences, all necessary. Front-loaded with primary purpose. No redundant or superfluous text. Efficient and clear.

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?

Despite no output schema, description sufficiently explains return values (category, rating, review_count, geo) and special cases. Complete for a single-item retrieval 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 covers place_id with 100% description. Description adds value by explaining return field semantics (category format, rating null meaning, geo null for service-area), which is beyond 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?

Description clearly states verb 'Get', resource 'stored Google Maps business', and identifier 'by Google place_id'. Distinguishes from sibling tools like datasets_google_map_search by emphasizing single-item retrieval via a specific ID.

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?

Context implies usage for looking up a specific business with known place_id, but no explicit when-to-use vs when-not or mention of alternatives. Lacks clear guidance on when to choose this tool over search or nearby tools.

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