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

Annotations already declare mutation (readOnlyHint false), idempotency, open-world, and non-destructive behavior. The description adds that the session must be open and that the booker is required to finalize a reservation, but omits auth needs or what happens if the session is closed.

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 tightly written sentences: the first defines the action, the second explains its timing and necessity. No redundant information.

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?

For a mutation tool with nested parameters and no output schema, the description is incomplete: it does not document the required identifiers or the booker object structure, and does not state what happens on success or failure.

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% and the description only identifies the 'booker' concept, leaving the id, meta, booking.id, and individual booker fields (email, name, phone) unexplained. It adds minimal meaning beyond the raw 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 a specific verb ('Enregistre') and resource ('le client qui réserve') on an open session, distinguishing it from read/create siblings in context. It does not name the sibling, but the timing ('après l’ouverture') makes the role clear.

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 timing context ('après l’ouverture de la session') and the need for booker to conclude a reservation, which implies when to call it. However, it does not explicitly contrast with alternatives like create_booking_session or get_booking_session, so the agent must infer.

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