querySubMembers

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

With no annotations, the description fully discloses behavior: returns all sub-accounts in single response (no pagination), includes UTA status, account mode determination logic, and detailed process flow. This provides complete transparency about what the tool does and its internal logic.

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 well-structured with sections and bullet points, but it is verbose, including detailed implementation steps (process flow) that may not be necessary for an agent. It could be more concise by focusing on input/output and key constraints rather than internal query logic.

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?

Given the complexity of the tool (multiple sub-account types, UTA mode logic, and no output schema), the description is very complete. It explains return fields, account types, statuses, modes, and differences from V5, covering all necessary information for an agent to use it correctly.

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 schema coverage is 100% (empty). Per the guidelines, baseline for 0 parameters is 4. The description adds value by explaining the context of the operation but does not need to document parameters. It covers the purpose well beyond the schema.

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 retrieves a complete list of all sub-accounts under the master account, with specific verb 'Get' and resource 'sub-accounts'. It distinguishes from sibling tool querySubMembersV5 by noting the V5 uses cursor-based pagination, and explicitly identifies itself as V3, thus avoiding confusion.

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 explicitly states only master account can call, sub-accounts cannot, and lists use cases. However, it does not explicitly state when to avoid this tool (e.g., for large accounts that might benefit from pagination), though it mentions the V5 alternative. Slight room for improvement in exclusion guidance.

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