tyi_onboard

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

No annotations are provided, so the description carries full burden. It mentions 'FAST' but does not disclose behavioral traits such as authentication requirements, side effects (e.g., overwriting existing data), or rate limits. The tool likely creates or initializes a wallet, but this is not explicit.

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 short (three fragments), front-loading key information ('FAST. First-time setup only. NOT tyi_chat.'). Every word adds value, though it could benefit from a slightly expanded structure.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain what 'onboard' means, the purpose of the mnemonic and agent_name parameters, or the outcome of the operation.

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 60% (three of five parameters have descriptions), but the tool description adds no parameter information. The description consists only of fragments about usage, leaving parameter meaning entirely to the schema. For a tool with 5 parameters, this is insufficient.

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 'First-time setup only' and 'NOT tyi_chat', clearly indicating the tool is for initial onboarding and not for chat. This distinguishes it from the sibling tool tyi_chat, though the specific verb 'onboard' is not explicit.

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 explicitly says 'First-time setup only' (when to use) and 'NOT tyi_chat' (when not to use), providing clear usage context and excluding a sibling tool. However, it does not mention alternatives for subsequent setups.

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