get_all_wallets

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

No annotations are provided, so the description must bear full responsibility. It declares the tool retrieves data but does not confirm read-only behavior, mention pagination, performance impacts, or potential errors. The lack of side-effect disclosure leaves agents underinformed about safety.

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 brief at two sentences, but contains a minor typo ('asssets'). It is front-loaded with the core purpose, but could be more polished. Overall, it is concise without being overly terse.

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 tool is simple, has an output schema, and one parameter documented in the schema, the description is adequate but not complete. It does not hint at the archived filtering option or clarify that it returns all accessible wallets. While not missing critical info, it leaves room for improvement.

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 input schema already describes the sole parameter (is_archived) with a default and description, achieving 100% coverage. The tool description adds no extra semantic value beyond what the schema provides, so baseline 3 is appropriate.

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 wallets with balances, using a specific verb and resource. It distinguishes from sibling tools that perform other wallet operations like create, archive, or transfer. However, it does not mention the optional archived filter or explicitly differentiate from listing tools like list_groups.

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 provides no guidance on when to use this tool versus alternatives. It does not state prerequisites, when not to use it, or direct users to related tools like create_wallet or archive_wallets for other needs.

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