get_thirdparty_discount

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

No annotations are provided, so the description carries the full burden. It clarifies the scope (global discount, customer/supplier) but does not explicitly state that the operation is read-only, what the return format is, or whether any side effects occur. For a getter, the read-only nature is implied by the name, but the description adds no explicit safety or behavioral context.

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 sentence that is front-loaded with the verb 'Obtenir'. Every word earns its place, and there is no redundancy or unnecessary detail.

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?

The tool is simple with one parameter, but the description does not mention the return value or format (e.g., a number representing a percentage). It also does not differentiate from the sibling get_thirdparty_price_level, which could cause confusion. More detail about what 'global discount' means and what the agent should expect in response would increase completeness.

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 only has thirdparty_id with no description, so the description's mention of 'd'un client ou fournisseur' provides meaningful context that the ID represents a customer or supplier. It helps the agent understand the parameter's role and domain, partially compensating for the schema's 0% description coverage.

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 the global discount for a customer or supplier ("Obtenir la remise globale d'un client ou fournisseur"). This specific verb+resource combination distinguishes it from siblings like set_thirdparty_discount and get_thirdparty_price_level.

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?

Usage is implied by the verb 'get' and the presence of a sibling 'set_thirdparty_discount', but the description does not explicitly mention when to use this tool or why it should be preferred over alternatives. No exclusions or alternative references are given.

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