listChildOrganizations

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

Annotations already declare readOnlyHint=true, and the description adds value by specifying the exact return fields (balance, cost-per-minute, concurrency limit, dashboard access flags) and the permission scoping ('scoped to your reseller's permissions'). This goes beyond just labeling it read-only.

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 compact and front-loaded with the action and resource. It uses two informative sentences plus a 'Tags: Reseller' note, with no wasted words. Every sentence earns its place.

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?

Despite having no output schema, the description comprehensively explains what the tool returns and the scope. It covers all key aspects an agent would need to decide to call it, including the specific data fields and permission context. No significant gaps remain.

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?

The tool has zero parameters, and the empty input schema fully covers parameter documentation. The description adds no parameter info because none exists; the baseline of 4 for 0-parameter tools 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 clearly states the tool 'List all child organizations and their users' with a specific verb and resource, and details the returned data (balance, rate, concurrency, access flags). It distinguishes itself from sibling tools like listAgents and listPhoneNumbers by focusing on reseller child organizations.

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 description clearly implies the tool is for reseller-level operations, specifying 'under the reseller account' and 'scoped to your reseller's permissions'. However, it does not explicitly mention when not to use it or name alternative tools for other listing scenarios.

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