reset_sequence

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

No annotations provided, so description carries full burden. It only states it resets sequence numbers, but does not disclose potential side effects (e.g., impact on active orders, session state changes, required permissions). Minimal behavioral context.

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?

Single sentence is concise and front-loaded. No wasted words, but slightly under-specified for a potentially destructive operation. Still, brevity is not harmful here.

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?

Tool has one simple parameter, no output schema, but as a mutating operation on a session, the description lacks details on what reset entails (e.g., starting sequence at 1, impact on current state). Incomplete for safe agent use.

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%, and the parameter description in schema ('Venue name') is clear. The description adds no additional semantics beyond confirming the venue's role in the reset. Baseline 3.

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?

Description clearly states the action (reset), resource (FIX sequence numbers), and context (venue session). It distinguishes from siblings like check_fix_sessions and fix_session_issue by focusing on resetting sequence numbers.

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?

No guidance on when to use this tool vs alternatives, no exclusion criteria, no contexts mentioned. The description is purely a statement of action without any usage advice.

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