Rechercher des livraisons / CRA

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds that it returns a list of matching deliveries with pagination, which is useful but not deeply revealing. 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 concise and well-structured: a brief purpose statement, a categorized Args list, and a Returns line. It is front-loaded with the main purpose, though the Args list is somewhat redundant with the schema.

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 read-only search tool with 100% schema coverage and no output schema, the description provides a clear purpose, parameter overview, and return type. It lacks explicit details about date semantics or result field structure, but is otherwise sufficient for an agent to invoke correctly.

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 100%, so the baseline is 3. The description's Args section largely duplicates the schema, merely grouping parameters into keywords, entity filters, period, and pagination. It adds marginal context like 'entite liee' but no substantial new semantics.

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's function: 'Recherche des livraisons (comptes rendus d'activite) dans BoondManager' with filters by project, company, and period. The specific verb 'Recherche' and resource 'livraisons' distinguish it from sibling tools like boond_deliveries_get (single retrieval) and boond_deliveries_create (creation).

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 gives clear context for when to use the tool: searching for deliveries with optional filters. It implies broad lookup use but does not explicitly mention alternatives or when not to use it, such as using boond_deliveries_get for a specific record.

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