Livraisons d'un projet

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, so the safety profile is clear. The description adds that it retrieves deliveries and groupments, but does not disclose other behaviors like pagination, sorting, or what happens if no deliveries exist. It is adequate but minimal beyond 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 extremely concise: one sentence for purpose, then a structured Args and Returns section. No extraneous words. Front-loaded with the key verb and resource.

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?

With no output schema, the description should clarify the return structure. It states 'List of project deliveries' but does not detail fields or whether groupements are included. Given the tool's simplicity and sibling context, it is minimally adequate but could be more complete.

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 single parameter 'id' has 100% schema description coverage, so the schema already explains it. The description's Args section repeats that it is the project ID, adding minimal new meaning. Baseline 3 is appropriate because the schema carries the burden.

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 tool retrieves deliveries (CRA) and groupments for a project. The verb 'Récupère' and resource are specific. However, it does not distinguish from siblings like boond_deliveries_get or boond_deliveries_search, which might also retrieve deliveries but at different granularities.

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 for fetching deliveries of a specific project via the 'id' parameter, but it does not explicitly state when to use this tool over alternatives (e.g., boond_deliveries_get for a single delivery, or boond_deliveries_search for cross-project searches). No when-not-to-use or alternative guidance is provided.

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