Détails d'un(e) todolist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: invalid IDs cause the raw BoondManager error, IDs must come from boond_todolists_search rather than guesses, and the return is the entity JSON with attributes and relations. No contradiction with 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 compact, front-loads the core action, and uses short labelled sections ('Quand', 'Plutôt que', 'Returns') plus a bullet for error handling. Every sentence adds distinct information with no filler or redundancy.

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 no output schema, the description is complete: it covers the ID source, error behavior, and return shape, and the call sequence with boond_todolists_search. Nothing essential for correct invocation is missing.

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 schema covers the single id parameter at 100%, including the numeric pattern and description, so the baseline is 3. The description mainly restates that the ID is numeric and adds provenance guidance ('l'ID doit venir de boond_todolists_search'), but it does not add significant format or meaning beyond what the schema already provides.

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 opens with a specific verb and resource ('Récupère la fiche complète d'un(e) todolist par son ID numérique') and contrasts the full entity with the list summary, distinguishing it from boond_todolists_search. An agent can tell what this tool does and how it differs from its closest sibling.

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?

It explicitly states when to use the tool (after a search, to obtain attributes missing from the list summary) and when not to ('Plutôt que : boond_todolists_search si l'ID n'est pas connu'). It also names the alternative tool and clarifies that this tool accepts an ID, not a name.

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