getAdvanceEarnPosition

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

The description discloses that only active/settling positions are returned and explains the coin parameter's filtering behavior. Rate limit is provided. However, it does not explain cursor-based pagination, the meaning of productId, or any potential errors.

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 brief and front-loaded with the purpose. However, the 'DiscountBuy notes' header adds slight confusion and could be removed or integrated more naturally.

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 absence of annotations and output schema, the description is incomplete. It does not explain what the tool returns, how pagination works, or the meaning of all parameters. Essential behavioral details are missing.

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?

With 0% schema description coverage, the description should add meaning to parameters. Only the coin parameter is explained with an example. Other parameters like category, productId, limit, and cursor are not described, leaving significant gaps.

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 'Query your active positions' with a specific verb and resource. The tool name 'getAdvanceEarnPosition' distinguishes it from sibling tools like 'getEarnPosition'. However, the mention of 'DiscountBuy notes' is somewhat confusing and could imply category-specific behavior that is not fully explained.

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 does not provide any guidance on when to use this tool versus alternatives such as getEarnPosition. It mentions required permissions and rate limits but lacks context for tool selection.

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