Détails d'une notification

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description does not contradict these and adds that it returns detailed information, but does not disclose additional behavioral traits (e.g., auth requirements, rate limits).

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 a single, front-loaded sentence in French with no unnecessary words. Every part is essential to convey the tool's purpose.

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 lack of output schema, the description could specify the return structure or mention error cases (e.g., not found). It simply says 'informations détaillées', which is vague. However, for a simple get operation, this might be acceptable.

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 100% description coverage for the single 'id' parameter, defining it as the unique identifier. The description only mentions 'par son ID', adding no new meaning 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 title 'Détails d'une notification' and description 'Récupère les informations détaillées d'une notification par son ID' clearly indicate a specific verb (retrieve) and resource (notification by ID). This distinguishes it from sibling tools like 'boond_notifications_search'.

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 specifies retrieving by ID, implying the agent needs the ID. The existence of 'boond_notifications_search' for searching without an ID provides implicit guidance, but no explicit when-not-to-use or alternative context is given.

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