get_user_two_factor_status

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

With no annotations, the description carries the disclosure burden. It does add genuine context by flagging that this requires self-hosted deployment and admin privileges, and "Get" implies a read. But it never states whether the call fails for unknown users, what an unenrolled user looks like, or what the response contains, which matters given no output schema.

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?

A single front-loaded sentence with the operation first and the access constraint second - zero waste. It is arguably too terse for a tool with no annotations and no output schema, but nothing in it is padding.

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 low-complexity, single-required-parameter read tool, so the short description is close to sufficient. The main remaining gap is that without an output schema it never hints at what the status value looks like (enrolled vs not, method, timestamps).

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 0% and the lone parameter userId has no documented format in the description. The phrase "a user's" weakly points at which identifier is expected, but the description adds no detail (e.g. UUID, where to obtain it) beyond what the schema's format field already implies.

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?

"Get a user's 2FA enrollment status" names a specific verb (get), resource (2FA enrollment status), and scope (a user's, not your own), which implicitly distinguishes it from the sibling get_two_factor_status. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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 real precondition for calling it, which is more than most siblings offer. However, it never says when to prefer this over get_two_factor_status (own status) or how it relates to set_user_two_factor_requirement / reset_user_two_factor, leaving the selection logic implied.

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