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

Annotations already declare readOnlyHint=false with destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: the write appends to a shared thread, attachments must already belong to the project (a hard constraint), and no generation is triggered as a side effect. Return/pagination behavior is not described, but no output schema exists either.

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?

Four short sentences, front-loaded with the core action, then constraints, then the side-effect boundary. Every sentence contributes information; nothing is padded or restated from the title.

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 6-parameter tool with a nested `target` object and no output schema, the description leaves meaningful holes: the purpose of `requestId`, the exclusivity rules inside `target`, and the text length limits are unaddressed. It is adequate to call the tool correctly in the common case but not complete for a complex nested write.

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%, so the description must carry the load, and it does for most params: it explains the `role` enum values, that `target` may be a page/section/block or a proposal page, and that `attachments` must reference project files. Gaps remain for `requestId` (an 8-128 char token that is almost certainly an idempotency key) and for whether pageId/pageSlug can be combined in `target`.

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?

States a specific verb and resource: append a message (user request or MonAssocie reply) to the site's shared thread. It distinguishes the two roles and the nature of `target`, so the agent understands this is thread-append, not generation. It does not explicitly separate itself from the similarly named siblings (send_conversation_message, get_conversation), so a 4 rather than a 5.

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 closing sentence 'Cette action ne lance pas de génération' implies a boundary — use delegate_task_to_monassocie or apply_site_proposal if you want generation — but no alternative tool is named. Role semantics (user = request, assistant = reply) give partial usage context, though there is no explicit when-to-use/when-not statement.

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