find_museum_guide

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

With no annotations, the description fully covers behavior: it searches a catalogue, returns specific data (2026 ticket info, hours, etc.) and is presumably read-only. No mention of side effects or destructive actions, which is appropriate.

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 sentences: first explains purpose and output, second gives usage examples. No extraneous information, front-loaded with key details.

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 explicitly lists what is returned (ticket info, opening hours, etc.). Three optional parameters are common and well-documented. Sufficient for an agent to understand when to use and what to expect.

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 already describes all three parameters (query, city, country) with 100% coverage. Description adds no additional semantics beyond listing example queries, which is already implied by the schema descriptions.

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 it searches travel.art's catalogue of museum visitor guides, lists specific return fields (ticket info, hours, address, etc.) and provides concrete example queries. Differentiates from siblings (find_art_events, recommend_art_trip) by focusing on museum visit logistics.

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?

Provides explicit usage examples like 'how to visit the Louvre' that clarify when to invoke. Does not explicitly state when not to use or contrast with siblings, but the examples strongly imply its specific domain of museum guides.

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