set_global_two_factor_requirement

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

With no annotations, the description carries the full burden. It usefully discloses that this is an admin-only global mutation, but it does not explain the impact on existing users, whether the change is reversible, or what the response indicates.

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 compact sentence with no filler, and the global scope and admin-only constraint are front-loaded.

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 simple one-parameter tool, the description covers the core purpose and permission requirement. However, as a security-sensitive global mutation with no annotations and no output schema, it should explain user impact or side effects more fully.

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?

There is one boolean parameter named 'required' with 0% schema description coverage. The phrase 'Require or stop requiring' implies the boolean mapping, but the description does not explicitly state that true enforces and false disables the requirement.

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 states a specific action (require or stop requiring 2FA) and scope (globally), and 'globally' distinguishes it from sibling tools like set_user_two_factor_requirement and set_team_two_factor_requirement.

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 parenthetical 'self-hosted admin only' gives a clear usage prerequisite, and 'globally' implies it is not for per-user or per-team settings. It does not explicitly name the alternative sibling tools, but the selection context is clear.

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