Informations générales d'un contact

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context on the type of data returned (contact details), but does not discuss error handling, missing IDs, or permissions.

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 concise with two succinct sentences. It uses a structured Args/Returns format, making it clear and easy to parse without unnecessary text.

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 retrieval tool, the description lists examples of returned data (coordonnées, société, fonction, tags) and annotations cover read-only and idempotent behavior. The absence of an output schema is partially compensated by these examples.

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 covers 100% of parameters, with the id parameter described as 'Identifiant unique de l'entité BoondManager'. The description restates it as 'ID du contact', adding minimal value 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 clearly states the tool retrieves general contact information (coordonnées, société, fonction, tags) and the verb 'Récupère' indicates a read operation. It distinguishes from siblings like boond_contacts_get, boond_contacts_invoices, etc., but does not explicitly differentiate between them.

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 provide guidance on when to use this tool vs alternatives such as boond_contacts_get or boond_contacts_search. It only states what it does, leaving the agent to infer the appropriate context.

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