tyi_reset

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

Without annotations, the description carries the burden. It clearly indicates a destructive action ('Wipe') and mandates a confirm parameter, implying irreversibility. However, it lacks details about what exactly gets wiped (e.g., all data, config, etc.) or any side effects.

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, using three short statements. It is front-loaded with the primary action. However, it lacks full sentences and could be slightly more structured for readability.

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's simplicity (one parameter, no output schema), the description covers the essential action and the required confirmation. However, it does not explain the full scope of the wipe operation or any potential consequences, leaving some ambiguity.

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 100% with the boolean parameter 'confirm' described as 'Must be true'. The description repeats this ('confirm:true required'), adding no new information beyond what the schema already provides.

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 'Wipe ~/.tyi' clearly states the action (wipe) and the resource (~/.tyi). The additional 'NOT tyi_chat' helps differentiate this tool from a sibling, making the purpose unambiguous.

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 mentions 'confirm:true required' which specifies a necessary usage condition, but it does not provide explicit guidance on when to use this tool versus alternatives like tyi_chat or other siblings.

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