mailu_update_user

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

No annotations are provided, so the description carries the full burden. It states 'updates' but does not disclose whether it performs a partial or full replacement, permissions required, or side effects. This is minimal disclosure for a write operation with many parameters.

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 a single sentence, concise but informal with ellipsis. It could be more structured and precise, especially given the number of parameters.

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?

Given 21 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error handling, or the scope of updates. Complex tool needs richer context.

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 low (19%). The description lists example fields but adds no additional meaning beyond the schema. For 21 parameters, this is insufficient to help an agent understand all options.

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 'Met a jour une boite mail' (Updates a mailbox), indicating a specific verb and resource. It lists examples (password, quota, forward, auto-reply) and distinguishes from sibling tools like create_user and delete_user.

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 implies usage for modifying an existing mailbox but provides no explicit guidance on when to use versus alternatives, no prerequisites, and no exclusions. Usage is implied but not detailed.

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