get_tpsl

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

Annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) already indicate safe read behavior. The description adds value by detailing returned fields (trigger prices, user addresses, triggered status), which supplements the annotations with concrete output 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, front-loaded with key information (verb, resource, tier, return fields). No unnecessary words. Highly efficient.

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 output schema exists, so return value details are covered. The description mentions the returned fields and tier restriction. Missing explicit mention of pagination (cursor, limit) and filtering (user, triggered) but these are in the schema. Complete enough given structured fields.

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?

Input schema has 100% description coverage for all 7 parameters, each with clear descriptions. The tool description does not elaborate on any parameter details beyond what the schema provides, so it neither adds nor detracts significantly. 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?

Clearly states the tool retrieves Hyperliquid TP/SL order history, lists the fields returned (trigger prices, user addresses, triggered status), and specifies the Pro+ tier requirement, distinguishing it from sibling tools like get_hip3_tpsl and get_hip4_tpsl.

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?

Mentions 'Pro+ tier' implying access restrictions but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are named among the many sibling tools, and pagination/filtering aspects are not mentioned.

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