reset_paper_account

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

With no annotations, the description discloses destructive behavior and the confirm requirement. However, it does not explain what happens if confirm is false (likely no-op) or return values, nor does it mention irreversible consequences.

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?

Two front-loaded sentences with no wasted words. The purpose is stated first, followed by the key requirement. Ideal for quick parsing.

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 is mostly complete. It could mention that the operation is irreversible or that it should be used with caution, but the core information is present.

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 schema has 0% description coverage for the single parameter 'confirm'. The description adds critical meaning by stating 'Requires confirm=true', indicating that the reset only executes when true. This clarifies the otherwise bare type and default.

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 action (reset) and resource (paper account), specifying it erases simulated history and returns to starting capital. This distinguishes it from sibling tools like fetch_paper_portfolio or place_paper_order that do not reset.

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 the requirement 'confirm=true', implying when to use it, but does not explicitly state when not to use it or suggest alternatives. Context around prerequisites (e.g., being in paper trading mode) is missing.

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