start_operator_passkey_enrollment

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

The description notes the link is 'short-lived' and requires email verification, adding context beyond a simple mutation. But it omits specifics like link expiration duration, one-time use, or error behavior if preconditions are not met.

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 sentences, no wasted words. The first sentence conveys the core function, the second adds a critical prerequisite. Maximally concise for the information provided.

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 parameterless tool with no output schema, the description covers the main action and a precondition. It lacks details on timeout or side effects, but is otherwise sufficient for basic agent understanding.

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?

With zero parameters and full schema coverage, the description's role is to explain the tool's operation without parameter details. It fulfills this adequately by stating the action and prerequisite.

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 action: email a passkey enrollment link. It specifies the target (operator, verified contact email) and distinguishes from sibling passkey tools like delete_passkey or passkey_register_options.

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 prerequisite 'Requires email_verified' is stated, providing a conditional. However, no explicit guidance on when to use this tool versus alternatives like passkey_register_options or when to proceed to verification.

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