Get resellers

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permissions, pagination, truncation, or what happens when parentAccountId has no resellers or is invalid. The single scoping phrase about parentAccountId is the only added context.

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?

One short clause with no filler, and the key scope qualifier is front-loaded in the same breath as the verb. It is efficient, though arguably under-specified rather than well-edited.

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 list-style retrieval tool with no annotations and no output schema, the description should at least hint at what comes back (fields, ordering, result size). It supplies none of that, leaving the agent with only the input constraint.

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 100% and the sole parameter already documents itself as 'Parent Account ID'. The description only repeats that name in a relational phrase, adding no format, type, or constraint detail beyond the schema, so baseline 3 applies.

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 pairs the verb 'GetResellers' with the resource and adds a scoping relation ('under parentAccountId'), which implies a filtered list rather than a single fetch. But it largely restates the tool name and title, and it never says explicitly that it returns a collection or how it differs from the singular sibling get_reseller.

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 statement of when to use this versus get_reseller, get_reseller_by_vat_id, or create_reseller/update_reseller, all of which appear in the sibling list. The only implicit cue is the plural resource name; nothing tells the agent about prerequisites or exclusions.

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