getTotalMembersAssets

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

The readOnlyHint and openWorldHint annotations already indicate a safe read-style operation; the description usefully adds authentication requirements, parentUid resolution behavior, and coin denomination behavior. It adds operational context without contradicting the annotations, though it omits rate limits and error behavior.

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 well-organized: a single front-loaded purpose sentence followed by three short, meaningful notes. There is no filler, and the bullet structure makes the key facts easy to scan.

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 one-optional-parameter read tool, the description covers purpose, auth, account scope, and coin semantics. However, it leaves the response shape undefined, does not state default denomination behavior, and the parentUid note is ambiguous given that the schema only allows coin and has additionalProperties set to false.

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?

With schema description coverage at 0%, the description must carry parameter meaning. It explains that coin, when specified, determines the asset denomination, which is useful. However, it references parentUid without defining it in the schema, and it does not explain the default denomination when coin is omitted.

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 a specific operation and resource: querying the aggregated total assets overview for parent and sub accounts. This makes the core purpose understandable, though it does not explicitly contrast the tool with overlapping sibling tools such as getAssetOverview or getWalletBalance.

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 communicates usage context through the parent-sub account support and the authentication requirement, so an agent can infer when the tool is relevant. However, it does not state when to prefer this tool over alternatives or when not to use it.

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