Opportunités d'une société

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful context beyond annotations: it returns a list, targets only the opportunities section, and explicitly notes 'Lecture seule'.

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 compact and well structured with labeled sections. The core action and purpose are front-loaded, and each sentence contributes a distinct piece of information without redundancy.

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 simple one-parameter read-only list operation, the description covers what the tool does, when to use it, which alternatives to prefer, and what it returns. The annotations handle safety semantics, and no output schema is expected for a straightforward list retrieval.

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% and the only parameter, 'id', is already well documented in the schema. The description simply confirms lookup 'par son ID', adding no significant meaning beyond the schema.

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 ('Récupère') with a clear resource ('les opportunités commerciales d'une société') and the required identifier. It is easily distinguished from sibling tools like boond_companies_get or boond_opportunities_search.

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 'Quand' section explicitly states the intended use case: loading only this section without the rest of the record. The 'Plutôt que' section names specific alternatives and the condition that selects each one (boond_companies_get for the base record, boond_companies_search when the ID is unknown).

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