fix_session_issue

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions three actions but doesn't explain what each does operationally (e.g., whether 'reset_sequence' is destructive, if 'reconnect' requires downtime, or what side effects occur). For a tool that likely modifies session state, this lack of detail is a significant gap.

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 extremely concise—a single sentence that efficiently states the purpose and lists the three actions. There's no wasted language, and it's front-loaded with the core function. Every word earns its place.

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 complexity of FIX session management, no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what 'resolving' entails, potential impacts, or expected outcomes. For a tool with two required parameters and likely critical operations, more context is needed.

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 description mentions 'resend_request (gap recovery), reset_sequence, or reconnect,' which partially explains the 'action' parameter's enum values. However, with 0% schema description coverage, it doesn't clarify the 'venue' parameter or provide deeper context for the actions. The description adds some value but doesn't fully compensate for the schema's lack of descriptions.

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 tool's purpose: 'Resolve a FIX session issue' with three specific actions. It uses a specific verb ('Resolve') and identifies the resource ('FIX session issue'), but doesn't explicitly distinguish it from sibling tools like 'reset_sequence' or 'dump_session_state' which might handle similar concerns.

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 provides no guidance on when to use this tool versus alternatives. It lists three actions but doesn't explain when to choose 'resend_request' over 'reset_sequence' or 'reconnect', nor does it mention when to use this tool instead of sibling tools like 'check_fix_sessions' or 'reset_sequence' (which appears as both an action here and a separate tool).

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