Generate Portal Self-Onboard Link

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so this is a non-read, non-destructive operation. The description transparently states the link is time-limited and single-use. It could elaborate on side effects (e.g., no client record created until registration), but overall adds value beyond annotations.

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 two clear paragraphs with bilingual text. It is front-loaded with the core purpose and includes role requirement and example. Minor redundancy from bilingual text reduces conciseness slightly, but overall it is well-structured.

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?

The tool has 4 parameters (1 required) and an output schema (not shown but present). The description covers purpose, role, example, and key behavior (time-limited, single-use). It does not explain the output format, but the output schema presumably covers that. Adequate for the complexity.

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 100%, so the schema already documents all parameters. The description adds value by providing a concrete example (email='...', expiresInHours=72) and bilingual context, helping the agent understand typical usage.

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 the tool generates a time-limited, single-use self-onboard invitation link for a prospective client. It distinguishes itself from sibling tools by specifying a unique purpose: client self-registration without manual data entry by the gestor.

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 explicitly requires gestor/admin role and provides a usage example. It does not explicitly list when not to use or alternatives, but the context is clear enough for an agent to decide.

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