list_suppliers

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It provides no information about whether this list is paginated, ordered, filtered, or requires any authentication. The description is identical to the tool name and offers no additional insight.

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, with no wasted words. However, it may be too brief; a slightly more informative sentence could improve clarity without sacrificing conciseness. It fits in one line and is front-loaded.

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 complexity (simple list tool with no params, no output schema, no annotations), the description is the sole source of information. It is minimal and leaves out key context about what the tool returns or any limitations, making it incomplete for reliable agent use.

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 zero parameters and 100% schema description coverage. With no parameters to describe, the description is not required to add parameter semantics, and the baseline is 4. It does not miss anything in this dimension.

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 verb 'list' and the resource 'suppliers' (in French), making it easy to understand the tool's main function. However, it does not distinguish itself from similar sibling tools like 'list_clients' or 'list_products', which would make it more helpful for an agent deciding between them.

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?

No guidance is provided on when to use this tool versus alternatives. With multiple list_* siblings, the agent would benefit from context on what this tool specifically covers or any special conditions, but the description offers none.

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