probely_disable_2fa

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

Minimal description with no behavioral details. No disclosure of side effects, reversibility, or required permissions. Annotations absent, so description should cover these.

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?

Single sentence with no extraneous text. Efficient but lacks substance.

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?

Even though tool is simple, the description fails to explain what disabling entails (e.g., removes TOTP only? Other methods?). Output schema exists but not utilized.

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 has 0% parameter description coverage, and the description does not elaborate on the meaning or format of targetId beyond the generic word 'target'.

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?

Description clearly states action (disable) and resource (2FA/OTP for a target). Distinguishes from sibling probely_configure_2fa_totp which likely enables 2FA.

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 on when to use this tool over alternatives. Does not mention prerequisites or context like requiring user permissions or current 2FA status.

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