Update reseller

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the "WRITE" label adds nothing structured data doesn't cover. The description omits the behaviors that matter for a mutation: whether the update is partial (merge) or replaces the whole reseller, what happens to omitted fields, and any permission requirements.

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?

Two short sentences with the mutation flag front-loaded and the payload instruction second, in the right order. Minor waste in restating the tool name as "UpdateReseller" before saying anything new.

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 write tool taking a free-form nested object with no output schema, the description should say whether unspecified fields are preserved and what a successful response contains. None of that is present, so an agent must guess at merge semantics before invoking a mutation.

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 coverage is 100% but only nominally: the reseller object is additionalProperties with no defined properties, so the schema itself reveals nothing about its contents. The description compensates by naming accountId as the identifier and stating the remaining keys are "fields to change", which is genuinely additive given the opaque nested payload.

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 verb+resource is stated ("WRITE: UpdateReseller"), but it largely restates the tool name/title rather than describing the operation in its own terms. It adds the payload shape but never says what kind of reseller fields are being changed or what the outcome is, and it does not distinguish itself from create_reseller or 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?

The "WRITE:" prefix signals a mutation, but there is no guidance on when to use this versus create_reseller (for new resellers) or when an update is not appropriate. No prerequisites, no exclusions, no mention of a retrieval step to obtain accountId first.

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