resellers_list

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

With no annotations, the description carries the behavioral burden, but 'List' and 'all' clearly signal a non-mutating enumeration with no hidden filtering or side effects. It does not describe pagination or access scope, yet for a zero-parameter, read-only listing with an output schema, the core behavior is transparent enough.

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 short sentence: 'List all reseller accounts.' The verb, object, and scope qualifier are front-loaded with no filler or redundant phrasing.

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 parameterless list operation with an output schema, this description is sufficient for an agent to invoke it correctly with no arguments. The scope is clear, return values are covered by the output schema, and there are no hidden configuration requirements.

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?

The input schema is empty with zero parameters, so schema coverage is effectively complete and no parameter semantics are needed. The baseline for zero-parameter tools is 4, and nothing in the description lowers that.

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 uses a specific action verb ('List') and a precise resource ('all reseller accounts'), clearly distinguishing it from sibling resources like users_list, admins_list, and resellers_get_config. The qualifier 'all' clarifies the scope as an enumeration rather than a detail/config lookup, exceeding a mere restatement of the tool 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?

The intended use is implied by the verb and resource: call this when you need to enumerate reseller accounts. However, it does not explicitly name alternatives or exclusions, such as when to prefer resellers_get_config or users_list, so the routing guidance is implicit rather than explicit.

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