foursquare_search_places

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or output format. The phrase 'Search for places' is too vague to inform the agent about side effects or restrictions.

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 extremely concise (4 words), but this under-specification is not beneficial. For a tool with 5 parameters and multiple siblings, it should include more structured information like parameter roles or usage examples.

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 the tool's complexity (5 parameters, no output schema) and presence of sibling tools, the description is completely inadequate. It does not explain what the tool returns, how to construct queries, or when to prefer it over other Foursquare tools.

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 only 20% (only 'll' has a description). The tool description adds no parameter explanations beyond what the schema provides, leaving 4 out of 5 parameters undocumented. The agent must infer the purpose of 'query', 'near', 'limit', and 'api_key' from the tool name.

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 verb 'Search' and the resource 'places' on Foursquare. However, it does not distinguish itself from sibling tools like foursquare_autocomplete or foursquare_get_place, which may have overlapping functionality.

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 provides no guidance on when to use this tool vs alternatives (e.g., foursquare_autocomplete, foursquare_get_place). There is no mention of prerequisites like an API key or context for choosing this tool.

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