Actions liées à un contact

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by stating 'Lecture seule', the return shape ('Liste des actions'), and the specific action subtypes, though it does not discuss pagination or error behavior.

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 blocks for purpose, when-to-use, alternatives, and returns. Every sentence earns its place and the core operation is front-loaded.

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 one-required-parameter, read-only list fetch, the description is complete: it identifies the resource and ID requirement, explains when to use it versus siblings, and states the return type as a list of actions. The absence of an output schema is mitigated by the clear 'Liste des actions' statement.

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 fully documents the single 'id' parameter with a numeric pattern and a clear entity-identifier description, giving 100% schema coverage. The description only says 'par son ID' and does not add semantic detail beyond the schema, so baseline 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 first sentence states a specific verb ('Récupère'), a precise resource (actions of a contact), and enumerates the action types (calls, emails, appointments, notes). It explicitly distinguishes itself from boond_contacts_get and boond_contacts_search in the 'Plutôt que' line.

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' clause gives a concrete trigger: load only the actions section rather than the full contact record. The 'Plutôt que' clause names the two relevant alternatives and the condition for choosing each one.

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