pulse_trader_closed_positions

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

No annotations provided, so burden falls on description. Mentions legacy table but does not disclose specific behavioral traits like pagination behavior, performance implications, or data completeness beyond noting it is superseded. Adequate but not rich.

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 sentences, each serving a distinct purpose: purpose and usage guidance. No redundant or extraneous content.

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 5 parameters but no output schema. Description covers purpose and usage well but lacks description of return format or data structure. Parameter descriptions are detailed, slightly compensating. Minor gap.

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 detailed descriptions for all 5 parameters. Description does not add additional context beyond schema; baseline 3 is appropriate.

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 explicitly states verb (history) and resource (closed positions for a wallet), with specific data fields listed. Clearly distinguishes from sibling pulse_trader_lifecycles by labeling itself as legacy.

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?

Explicitly advises preferring pulse_trader_lifecycles for better data, and notes backward compatibility reason to keep this tool. Provides clear when-to-use and when-not-to-use guidance.

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