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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered by structured data. The description adds one genuinely useful behavioral fact beyond that: the response is an aggregate spanning consents, history, campaigns, payments and trainings, implying multiple sections returned in one call. It says nothing about size, pagination or permissions, so it stays at a moderate level.

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?

It is a single short fragment with no wasted words, but it is under-specified rather than well-structured: no leading verb, no sentence, and the key subject (contact) appears only in the tool title. Brevity here comes at the cost of clarity.

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?

With no output schema, the description carries the burden of explaining what comes back; it does list the content areas, which is partial help, but it never identifies the required identifier or the contact-centric scope. For a read tool fetching a full record, that leaves essential calling information missing.

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 0% for the single required parameter 'id', and the description never mentions it. An agent cannot tell from the definition whether 'id' is a contact id, a user id or something else, so the description fails to compensate for the schema gap.

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 is a noun phrase listing content sections ('fiche complète, consentements, historique, campagnes, paiements et formations') with no verb, so the action (fetch a consolidated contact view) is inferred from the title rather than stated. It does hint at the composite nature of the resource, which helps separate it from atomic siblings like get_record or get_contact_form_responses, but the distinction is only implicit.

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?

There is no when-to-use guidance at all: nothing says when to call this overview versus get_record, get_contact_form_responses, list_crm_form_responses, or the campaign/payment siblings. The agent must guess from the enumerated sections that this is the broad, first-look tool.

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