resellers_get_config

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

No annotations are provided, so the description carries the full burden of disclosing behavior. 'Reseller configuration.' does not indicate whether the call is read-only, requires special permissions, or has side effects. It provides no behavioral disclosure beyond what the tool name already implies.

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 structurally clean, but the first line 'Reseller configuration.' mostly restates the tool name and does not earn its place. The Args block is the only substantive content, making this under-specification rather than effective conciseness.

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?

With one required string parameter and an output schema, the tool is simple, but the description still lacks enough context for an agent to confidently route to it among many sibling tools. It does not explain what configuration data is returned, whether the operation is safe, or how it differs from related getter tools. This is below minimum viable completeness.

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%, but the Args line adds meaning by clarifying that `username` is 'Reseller name', which is a useful semantic over the schema's generic 'Username' title. However, it stops there: no format, example, or validity constraint is provided, so it only partially compensates for the missing schema descriptions.

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 reads 'Reseller configuration.' which identifies the resource but does not state an action like 'get', 'retrieve', or 'list'. The verb only appears in the tool name itself, leaving the actual purpose vague and indistinguishable from sibling tools such as users_get_config or resellers_get_usage.

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 use this tool versus alternatives. The description does not mention selecting this over users_get_config, resellers_list, or resellers_get_usage, nor does it state any prerequisites or context. The only added content is a parameter note, not usage direction.

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