delete_signup_by_user

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

With no annotations, the description carries the full burden and does disclose two non-obvious behaviors: send_emails defaults to true and triggers email notification, and without confirm=true the call is a dry-run preview. It omits permissions and reversibility, but the dry-run gating and side-effect disclosure are substantive for a destructive 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?

Three short sentences, front-loaded with the action and followed by the two behavioral caveats. Dense with no filler; only slightly terse given the destructive nature of the tool.

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 destructive, 5-param tool with no annotations and no output schema, the description covers the key safety behaviors (dry-run, email side effect) but omits what a preview returns, what happens to the deleted record, and permission requirements. Adequate but with clear gaps.

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% across 5 params, so the description must compensate and only partially does: it explains send_emails (default true, sends email) and confirm=true (preview gating), covering 2 of 5. date, user_id and field_id are left entirely to their self-descriptive titles.

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 (supprime/delete) and resource (inscription d'un membre dans un champ donné d'une journée), so an agent knows it removes one member's signup for a specific field/day. It is clear, but it does not explicitly distinguish itself from the closely-named siblings delete_signup and delete_all_field_signups, which the agent must infer.

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 confirm=true / preview-only note gives practical usage guidance for the delete flow, but the description never states when to choose this tool over delete_signup or delete_all_field_signups. Usage is implied rather than routed against alternatives.

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