delete_tour

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

With no annotations, the description carries full burden. It only states 'Supprimer un tour' (delete a tour), but does not disclose if deletion cascades to associated data, if it is immediate/permanent, or what checks occur. A destructive operation like this needs more 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 very short (one sentence + Args). It is concise but lacks necessary depth. The structure is minimal, with the Args section repeating the schema. It earns its place only as a basic purpose statement.

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 presence of an output schema (not shown) and one required parameter, the description is incomplete. It does not explain return values, success/error behavior, or permissions. For a deletion tool, this is insufficient for an agent to use it safely.

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 0% because the description repeats the parameter name ('tour_id') and its role ('ID du tour a supprimer') which is identical to the schema property title 'Tour Id'. It adds no additional meaning such as format, constraints, or examples. For a single required parameter, the description should provide more value.

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 'Supprimer un tour' clearly states the action (delete) and resource (tour). It distinguishes from sibling tools like update_tour or create_planned_tour. However, it is minimal and could be more explicit about what exactly is deleted.

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. It does not mention prerequisites, whether deletion requires authorization, or if the operation is reversible. The only context is the parameter, which is already in the schema.

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