Set Mfa

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

The description does not disclose side effects, state changes, or requirements beyond a phone number. Annotations indicate destructive=true and readOnly=false, but the description adds no behavioral detail about what setting MFA entails.

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 concise and contains no fluff, but the single sentence is more of a caveat than a functional description. It is short but sacrifices necessary clarity.

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 lacks essential context: no output schema, no explanation of the request body's purpose, no mention of verification flow, and no indication of what happens when MFA is set. The description is incomplete for an agent to use it correctly.

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 defines a boolean 'mfaEnabled' inside a requestBody, but the description does not explain the meaning of this field. It is unclear whether true enables MFA, false disables it, or if other semantics apply.

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 title 'Set Mfa' is vague, and the description only states a precondition ('Enabling it requires a verified phone number') without explicitly saying what the tool does. It does not clearly indicate that this sets or updates the MFA enabled/disabled state.

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?

No guidance is provided on when to use this tool versus alternatives like verifyPhone or startPhoneVerification. The description mentions a precondition but does not explain the intended workflow or when this should be called.

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