choose-your-wallet-mode

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

No annotations exist, but the description indicates a read-only educational action. It does not disclose output format or side effects, which is acceptable for a lesson tool as no destructive actions are implied.

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 two concise sentences that immediately convey the tool's purpose and content. No unnecessary words.

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 an educational tool with no parameters and no output schema, the description adequately explains its content. It could mention what the user can expect (e.g., a list or interactive guide) but is complete enough.

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?

No parameters are defined, so the baseline is 4. The description does not need to add parameter information since there are none.

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 that this tool is a lesson covering four wallet modes and how to choose between them. It differentiates itself from sibling tools like 'get-a-wallet' (which likely creates a wallet) and 'what-is-a-wallet' (which explains basics).

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 use when needing to understand wallet mode selection, but does not explicitly state when to use versus alternatives or provide exclusions. The context is clear but not prescriptive.

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