Get reseller

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

No annotations are provided, so the description carries the full burden, yet it says nothing about permissions, whether the lookup fails when the account is absent, or what data class is exposed. The "Get" verb weakly implies a read-only lookup, but nothing beyond that is disclosed.

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?

It is short and front-loaded, but at the cost of being under-specified — the single sentence largely duplicates the title and name rather than earning its place with useful detail.

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?

There is no output schema, so the description should at least indicate what a "reseller" record contains or whether the call errors on unknown accounts. Neither is covered, leaving the agent unable to anticipate the response for a simple but under-explained lookup.

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 single accountId parameter is documented as "ALSO Cloud Account ID" in the schema. The description's mention of accountId adds no semantics beyond that, so the 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 is essentially a restatement of the tool name plus the lookup key: "GetReseller — reseller by accountId." It states the resource and identifier but adds no differentiation from siblings like get_resellers, get_reseller_by_vat_id, or get_company; the accountId detail is already in the schema.

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 versus get_resellers (list) or get_reseller_by_vat_id (VAT lookup), which are the obvious alternatives. An agent must infer the choice purely from the shared accountId parameter.

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