start_operator_passkey_enrollment

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

The description discloses that the link is 'short-lived' and emails 'the verified contact email'. With no annotations, it provides some behavioral traits, but does not mention what happens if email is not verified, whether it is idempotent, or what the tool returns. It adds value beyond the empty schema but lacks full transparency.

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 that immediately conveys the action and key constraint. It is concise with no wasted words.

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 no output schema, the description covers the basic action but leaves out details like return value (e.g., success indication), error handling, or the duration of the 'short-lived' link. It is adequate for a simple tool but not comprehensive.

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?

The input schema has 0 parameters, so schema description coverage is 100% by default. The description does not need to add parameter info, and it doesn't. Baseline is 4 for zero parameters.

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 it emails a short-lived passkey enrollment link for an operator. It specifies the resource ('operator passkey enrollment') and action ('Email'), but does not explicitly distinguish from sibling tools like 'passkey_register_options' or 'set_agent_contact', though mentioning 'operator' provides some differentiation.

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 mentions a precondition 'Requires email_verified', which gives context on when the tool can be used. However, it lacks guidance on when to use this tool versus alternatives such as 'passkey_register_options' or 'request_magic_link', and does not state when not to use it.

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