list_receptions

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

No annotations are provided, and the description only says 'List supplier receipts.' It does not disclose pagination behavior, status filter semantics, sqlfilters usage, response format, or whether any side effects occur, leaving most behavioral expectations unspecified.

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 concise phrase with no wasted words, but it lacks any structured context or elaboration. It is efficient but borderline under-specified for a tool with multiple parameters and no other documentation.

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 list operation with four optional parameters, no annotations, and no output schema, the description only provides the basic purpose. Important contextual information such as pagination behavior, status filter options, and result structure is entirely absent.

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 four parameters (page, limit, status, sqlfilters) with 0% description coverage, and the description does not explain any of them. The agent is left to infer the meaning of status codes or SQL filter syntax, so the description adds no value to parameter understanding.

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 uses a specific verb 'Lister' and a specific resource 'réceptions fournisseurs' (supplier receipts), clearly identifying it as a list operation. It is unambiguous and naturally distinguished from the singular get_reception 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?

The description gives no guidance on when to use this tool versus alternatives such as list_shipments or get_reception, nor does it mention any exclusions or filtering context. It states only the basic action.

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