get_hip3_tpsl

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds return content (trigger prices and triggered status) and a Pro+ tier note, which provides additional context beyond annotations.

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: first sentence states purpose and tier, second provides case-sensitivity hint and return summary. No redundancy, front-loaded, and every word adds value.

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?

The description covers purpose, tier, case-sensitivity, and return content. With an output schema present, it need not detail return structure. It lacks explicit mention of pagination or default time ranges, but those are in the schema. References to get_hip3_instruments enhance completeness.

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 parameter descriptions. The description adds extra value by stating case-sensitivity, giving market examples, and suggesting use of get_hip3_instruments to list symbols, going beyond schema details.

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 it retrieves HIP-3 TP/SL order history, specifies the Pro+ tier, and mentions case-sensitivity. It distinguishes itself from siblings like get_tpsl (general) and other get_hip3_* tools by focusing on TP/SL orders.

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 implies usage for HIP-3 TP/SL orders and notes the Pro+ tier requirement, but does not explicitly exclude alternatives like get_tpsl for non-HIP-3 or provide 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.