transferCreditsToChild

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

Discloses that credits are immediately deducted from the reseller balance on success, which goes beyond the annotation readOnlyHint=false. Also notes the direct-child constraint, giving important behavioral context. No contradiction with annotations since this is a write operation.

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?

Three concise sentences with the action front-loaded in the first sentence. Subsequent sentences add essential constraints and prerequisite without fluff.

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?

Covers purpose, side effect, and prerequisite, and points to the calculate endpoint. With the nested schema fully documented and annotations providing safety profile, description is complete enough for selecting and invoking the tool, though return-value details are absent.

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%, with each parameter (to_organization_id, minutes, cost_per_min) already described in the input schema. The tool description does not add new param details, so baseline 3 is appropriate.

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 clearly states 'Transfer minutes from the reseller balance to a child organization' with a specific verb and resource, and distinguishes itself from sibling tools like revertCreditsFromChild and calculateCreditOperation by focusing on the actual transfer action.

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?

Explicitly instructs to 'Use the calculate endpoint first to preview the cost', pairing with the calculateCreditOperation sibling. Also states the prerequisite that the target must be a direct child. Does not explicitly mention when not to use, but provides adequate contextual guidance.

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