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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond annotations by stating that results include current price, merchant, purchase link, and a Picksly page explaining the score.

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 front-loaded sentence that identifies the core task first and then lists the returned fields. There is no redundant or wasted language.

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 recommendation tool with no output schema, the description covers the essential behavior and return contents well. It is slightly incomplete in that it does not describe pagination, ranking methodology, or output structure, but the schema and annotations carry much of the remaining detail.

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 description coverage is 100%, so all seven parameters are already documented in the schema. The description echoes the category, buyer profile, and optional maximum budget but adds little semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific retrieval task: 'Best-rated models of a category for a buyer profile and an optional maximum budget.' This is much clearer than the tool name alone, but it does not explicitly distinguish the tool from siblings such as comparer_modeles or fiche_modele.

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 through the buyer-profile and budget filters, but it gives no explicit when-to-use guidance, prerequisites, or comparison against the sibling tools. An agent can infer the use case, but is not told when to prefer this over comparer_modeles or fiche_modele.

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