fix_session_issue

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

No annotations provided; the description should disclose behavioral traits. It mentions 'gap recovery' for resend_request but does not explain side effects, permissions, or state changes for the actions, which are likely mutating.

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 a single short sentence, making it concise. However, it lacks structure and reads as under-specified rather than efficiently packed with information.

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 simplicity of the schema (2 params, no output) and the complexity of the domain (FIX session recovery), the description is incomplete. It does not explain what each action entails or when each is appropriate.

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 description coverage is 0%. The description adds minimal meaning: it lists the action enum values but does not describe the 'venue' parameter (e.g., what it represents). The agent is left to guess venue's purpose.

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 verb 'Resolve' and resource 'FIX session issue', and lists three specific actions. However, it does not differentiate from the sibling tool 'reset_sequence', which overlaps with one of the actions.

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 versus alternatives like 'reset_sequence' or 'check_fix_sessions'. The description lacks any 'when to use' or 'when not to use' information.

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