Créer un(e) opportunité

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

The description confirms it creates a new opportunity and returns the created record with ID. While this adds a small behavioral detail, the annotations already convey that this is a write operation (readOnlyHint false). No additional side effects, authorization needs, or limitations are disclosed.

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 two concise sentences, front-loaded with the action and ending with the return value. No wasted words.

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 create tool with a rich schema and output schema, the description is minimal but sufficient. It identifies the purpose and return value, but lacks contextual guidance about prerequisites or workflow. Given the schema covers parameter semantics, the description meets the minimum viable level.

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?

All 15 parameters are fully described in the input schema with 100% coverage. The description adds no parameter-specific detail, so the baseline of 3 applies.

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 the specific verb 'Crée' (create) with the resource 'opportunité' and system 'BoondManager', clearly distinguishing it from sibling tools like boond_opportunities_update or boond_opportunities_delete. The title reinforces this, but the description adds 'nouvelle' and the system context.

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 does not explicitly state when to use this tool or how it differs from alternatives. The verb 'Crée' implies usage for new opportunities, but there is no direct guidance or exclusions, so it only provides implied usage.

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