add_signup

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

With no annotations, the description carries the full burden, and it does disclose the important side effect (automatic confirmation/waiting-list emails) and the preview-without-confirm behavior. However it omits auth/permission needs, duplicate-signup behavior, and reversibility, leaving meaningful gaps for a mutation tool.

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?

Two compact sentences that front-load the core action and then the key behavioral caveat. Little waste, though the parenthetical French param labels add some density without much added value.

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-param mutation tool with zero annotations and no output schema, the description covers the main action and the critical confirm/email behavior but leaves the date parameter, error cases, and required permissions unexplained.

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 coverage is 0%, so the description must compensate, and it does map several params (user_id, field_id, signup_parameter, signup_comment) to their roles and marks the latter two optional. But it adds no format or semantic detail, and the required 'date' param is only implied via 'journée'.

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 (inscrit/registers) and resource (a member/user_id into a field/field_id on a given day), which makes the operation concrete. It does not explicitly differentiate itself from the similar sibling add_freetext_signup, so an agent could still wonder which add-variant applies.

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 explains the confirm=true preview gate, which is useful, but gives no explicit when-to-use vs the many siblings (add_freetext_signup, add_freetext_signups_bulk, update_signup). No exclusions or selection conditions are stated.

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