create_venue

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

With no annotations, the description carries full burden. It discloses find-or-create behavior, enrichment, deduplication, and return of existing ID. Does not mention error handling, rate limits, or authorization, but core behaviors are clear.

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?

Three concise sentences front-load key info (purpose, enrichment/dedup, return behavior). No unnecessary words; every sentence adds value.

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?

Given complexity (8 params, no output schema, no annotations), the description covers core behavior and safety. Lacks detailed output structure, but mentions return of venueId. Adequate for practical use.

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 description coverage is 100%, so parameters are already well-documented. The description adds minimal extra semantics beyond the schema, such as noting Google Place ID is 'strongly recommended'. Baseline of 3 is appropriate.

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 finds or creates a venue, with automatic enrichment and deduplication via Place ID. It differentiates from the sibling 'search_venue' by noting it is safe to call without pre-checking, ensuring unique purpose.

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?

Explicitly states 'Safe to call without pre-checking via search_venue', guiding when to use this tool vs. search. However, lacks detailed instructions for specific scenarios like when not to use or prerequisites beyond required params.

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