get_stability_pool_accounts

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

With no annotations provided, the description carries the full burden. It indicates this is a read operation ('Get') and filters by 'open' status, but fails to disclose pagination behavior, response structure, or what distinguishes an 'open' account from other states.

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 single-sentence description is front-loaded with the primary action ('Get all open stability pool accounts') followed by the conditional clause ('optionally filtered by iAsset'). No redundant words or phrases present.

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 low complexity (one optional enum parameter, no nested objects) and absence of an output schema, the description adequately covers the input contract. It could be improved by briefly indicating the return type (e.g., array of account objects), but remains sufficient for tool selection.

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 schema has 0% description coverage. The description compensates by indicating the `asset` parameter is used for 'optionally filtered' filtering and implies optionality (consistent with the schema). It could further clarify that 'iAsset' refers to the synthetic assets listed in the enum values.

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 'all open stability pool accounts' with specific filtering capability. However, it does not explicitly differentiate from sibling `get_sp_account_by_owner` (which retrieves a specific account by owner rather than listing all open accounts).

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 phrase 'optionally filtered by iAsset' implies when to use the parameter versus retrieving unfiltered results, but provides no explicit guidance on when to use this tool versus alternatives like `get_sp_account_by_owner` for owner-specific lookups.

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