What is on in a French city on a given date — the typical "find me something to do tonight" query. Returns cultural events (theater, concerts, exhibitions…) with prices and reseller offer counts, cheapest first when a budget is given.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City name, e.g. "Paris" | |
| date | No | Defaults to today (Europe/Paris) | |
| budget | No | Max price per ticket in EUR | |
| category | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses return contents (events with prices, reseller offers) and sorting behavior (cheapest first when budget). With no annotations, still transparent enough for a read-only query.
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?
Two tight sentences. First sets purpose, second details behavior. 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?
Covers purpose, input, output (events with prices/offers), ordering. Lacks page size or limit, but adequate for a straightforward query 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 3 of 4 params. Description adds meaning: explains category by listing examples, describes sorting by price when budget provided. Adds value 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?
States specific verb-resource: find cultural events in French cities. Distinguishes from siblings like search_shows or find_venues which are more general or venue-focused.
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?
Clearly says 'typical find me something to do tonight query', implying use when user wants local events. Doesn't explicitly exclude use cases, but context clarifies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
