get_tour_directions

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

No annotations are provided, so the description alone should disclose behavioral traits. It does not mention that the tool is read-only, whether it requires any permissions, or what side effects exist. The description only states the function without behavioral context.

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: one sentence and an argument list. Every part is relevant, with no unnecessary or repetitive content.

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 low complexity (single parameter, simple retrieval) and the presence of an output schema, the description is sufficiently complete. It conveys the essential purpose and parameter, though it lacks details about return format or prerequisites.

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?

The input schema has 0% description coverage, but the tool description provides a brief explanation for 'tour_id' as 'ID du tour.' This adds minimal meaning beyond the schema's title 'Tour Id.' For a single parameter, this is adequate but not rich.

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 states 'Instructions de navigation turn-by-turn d'un tour planifié,' which clearly indicates the tool provides turn-by-turn directions for a planned tour. The resource (tour directions) and verb (get) are explicit, and it distinguishes from siblings like get_tour_coordinates and plan_route.

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 versus alternatives, no prerequisites, and no exclusions. It simply describes what the tool does without context on when it is appropriate.

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