Détails d'un contrat

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that it retrieves 'informations détaillées' by ID, which is a mild behavioral clarification but not deep context like error handling or response shape. It does not contradict annotations.

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 one concise, front-loaded sentence with no filler. Every word contributes to stating what the tool does.

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 simple get-by-ID tool with one parameter and robust annotations, the description is largely complete. It lacks an explicit statement of what 'detailed information' includes or error behavior, but the low complexity and clear 'by ID' scope make it sufficiently contextual.

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 fully describes the single parameter ('Identifiant unique de l'entité BoondManager (numérique)') with 100% coverage. The description's 'par son ID' reinforces that the ID refers to the contract, adding a small semantic linking, but it does not substantially go beyond the 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?

The description clearly states the verb and resource: 'Récupère les informations détaillées d'un contrat par son ID.' It specifies a singular contract by ID, distinguishing it from the sibling create tool and other getters. The title reinforces the same meaning.

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 implies usage when you have a contract ID and need its details, but it provides no explicit context about when to prefer this over alternatives or what to do if the ID is unavailable. No sibling search tool for contracts appears in the list, so the guidance remains implicit.

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