reset_mfa

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

With no annotations, the description must fully disclose behavior, but it only states 'User · mutation resetMfa.' This confirms it is a mutation but fails to describe what gets changed, whether it is destructive, what prerequisites exist, or what the response contains. The example variables are raw data, not behavioral explanations.

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 short but poorly structured, starting with a cryptic header, then a flat variable list, and a truncated example that runs on. The example is not formatted clearly and the cut-off text adds noise rather than helping the agent understand the request.

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?

This is a complex tool with 14 parameters, no output schema, and no annotations. The description provides almost no context about the operation's purpose, the role of each parameter group, or the expected response, making it completely inadequate for correct invocation.

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% (every parameter has a GraphQL type note), so baseline is 3. The description lists all variable names and provides an example JSON, but it does not clarify the semantics of parameters such as the required 'user' field or what the pagination-like filters (after, filter, first, order) control.

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 essentially restates the tool name ('mutation resetMfa') and labels it as user-related, but does not explain what resetting MFA entails. It lacks a specific verb phrase like 'Resets the multi-factor authentication configuration for the specified user,' making it a tautology of the name.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like update_user or generate_password_link exist, but the description does not distinguish this operation or provide context for when resetting MFA is appropriate.

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