choose-your-wallet-mode

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

With no annotations, the description carries the burden of disclosing behavior. It clearly indicates this is an educational lesson rather than a system action, which is helpful. However, it does not describe what the agent/user will see (e.g., text, steps), or whether it tracks progress. Acceptable but not rich.

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 very concise: two sentences that clearly state the lesson number, topic, and purpose. Every word earns its place, with no fluff or repetition.

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 simple lesson tool with no parameters and no output schema, the description is nearly complete. It names the lesson and the specific topic. However, it lacks explicit context about where this fits in the curriculum (beyond 'Lesson 16') or when an agent should invoke it relative to siblings.

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 tool has zero parameters, and the schema coverage is 100% (vacuously). No parameter details are needed, and the baseline for 0-param tools is 4. The description appropriately focuses on content rather than inputs.

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 it is a lesson about the four wallet-holding modes and how to choose among them. The resource is specific (wallet modes), and the verb is implied as 'teach/explain' via 'Lesson 16'. It is fairly clear and distinct from siblings, though it lacks an explicit action verb.

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 'how to pick' implies this tool is for deciding between wallet modes, providing some usage context. However, it does not explicitly contrast with alternatives like get-a-wallet or configure-wallet-skills, nor does it mention when not to use it. Guidance is implied but not explicit.

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