search_venue_then_get_user_stats

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

With no annotations, description carries full burden. It discloses the number of calls (1 search + scan) and feed page size (25/page), giving agents cost and pagination insight. Missing edge cases like no match or errors.

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 front-loads the action and includes key details (call count, page size). Efficient, no filler.

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?

Complex compound tool with no output schema. Description explains flow and scan strategy but omits output details and error handling. Adequate for basic use but missing completeness.

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 baseline 3. Description adds context that max_pages controls scan depth and defaults to 5. Does not elaborate on other parameters beyond schema, which is adequate but not exceptional.

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 compound action: search for a venue by name then get user stats at the top match. It distinguishes from siblings like venue_search (pure search) and get_user_stats_at_venue (requires venue 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?

The description explains when to use the tool (to both search and get stats) and implies the context (scanning feed). However, it does not explicitly state when not to use or mention alternatives like separate calls.

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