get_stability_pool_accounts

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

With no annotations, the description carries the burden of behavioral disclosure. It communicates that only open accounts are returned and that filtering by iAsset is possible, but it does not state whether results are paginated, what fields are returned, or explicitly confirm this is a read-only 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?

The entire description is one tight, front-loaded sentence with no filler. Every word adds value: 'all open' sets scope, 'stability pool accounts' names the resource, and 'optionally filtered by iAsset' covers the parameter.

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 low-complexity tool with one optional parameter and no output schema, this description gives the essential information an agent needs to invoke it. It could be more complete by naming sibling tools for single-account lookups, but that is a minor gap rather than a critical omission.

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 0%, so the description must add meaning to the parameter. It does this by identifying 'asset' as an optional filter and relating it to iAsset values, which the schema enum already enumerates. This is sufficient compensation for the single optional parameter.

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 states a specific verb ('Get'), a resource ('stability pool accounts'), and a precise scope ('all open'), while also mentioning the optional filter by iAsset. This clearly distinguishes it from related sibling tools like get_stability_pools or get_sp_account_by_owner.

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 implies the main use case—listing open stability pool accounts, optionally filtered by asset—but does not explicitly say when to use this instead of alternatives such as get_sp_account_by_owner or get_stability_pools. No exclusions or alternative conditions are provided.

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