resellers_convert_to_user

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

No annotations are provided, so the description must carry the behavioral burden. It does flag that confirmation is needed, but it does not explain what confirm actually does, whether the demotion is destructive/reversible, what happens to the reseller's existing accounts or resources, or what permissions are needed. The phrase 'confirm: Required' is also ambiguous and conflicts with the schema's optional default-false confirm field.

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 and front-loaded with the main purpose, and the Args section is cleanly separated. It loses a point because the 'confirm: Required' line is misleading and does not meaningfully explain the parameter.

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 privilege-demotion operation with no annotations, the description is incomplete. It lacks side-effect disclosure, alternative routing, and confirmation semantics. While an output schema exists, the core operational context an agent needs to safely invoke this confirmed, destructive-style action is missing.

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%, so the description must compensate. It defines 'username: Reseller to demote' clearly, which adds value, but 'confirm: Required' is not a semantic explanation and even contradicts the input schema where confirm is optional with a default of false. The description should clarify that confirm must be set true to proceed.

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 uses a specific verb ('Demote') and resource ('a reseller') plus the resulting state ('to a regular user'). This clearly distinguishes it from the sibling users_convert_to_reseller, which performs the reverse operation, so an agent can tell which tool is which.

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 about when to choose this tool over alternatives, no prerequisites, and no mention of related operations. The description only states the action itself, leaving the agent to infer usage context without support.

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