Créer un positionnement

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

The description explains the documented effect of creating a placement, complementing the annotations (readOnlyHint=false, destructiveHint=false). It does not disclose potential side effects, validation rules, or return behavior, but given the annotations cover the safety profile, the additional context is adequate but not rich.

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 with no unnecessary words. It efficiently conveys the action and purpose, earning a perfect score for conciseness.

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 an 8-parameter create tool with no required parameters and no output schema, the description covers the core purpose but leaves gaps: it does not specify the relationship between parameter groups nor mention the return value. The schema and annotations provide additional detail, making the description adequate but not exhaustive.

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 description adds conceptual meaning by explaining that the tool links either a candidate or a resource to either a project or an opportunity. This clarifies the parameter groups (candidateId/resourceId and projectId/opportunityId) beyond the individual schema descriptions, though it does not explicitly state required combinations.

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 ('Crée') and resource ('positionnement'), and clarifies the purpose: placing a candidate or resource on a project or opportunity. This clearly distinguishes it from sibling tools like update/delete/search and from entity-specific creation tools.

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 provides a clear usage context: use this when placing a candidate or resource on a project or opportunity. It does not explicitly mention alternatives or exclusions, but the context is well-defined and implicitly guides the agent on when to invoke the tool.

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