earn_get_position_movements

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

No annotations provided, but description describes return value (types, amounts, dates, status) and pagination with metadata. Marks [PRIVATE] indicating restricted access. Could mention read-only nature but overall adequate.

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?

Three concise sentences plus a tag, each adds value: purpose/output, pagination, prerequisite. No redundancy or fluff.

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?

Covers return fields and pagination but lacks specific response structure (e.g., keys). No error handling or auth details beyond schema. Adequate for a simple tool but could be richer given no output schema.

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 clear descriptions. Description reinforces that position_id comes from earn_get_positions and mentions pagination params. Adds minor value beyond schema.

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 'Get movement history of a specific Earn position' and lists returned data types (deposit, withdrawal, reward, fee). It distinguishes from siblings like earn_get_movements by specifying it's for a specific position.

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 to use earn_get_positions first to obtain the position ID. Also notes optional pagination parameters. Does not explicitly state when not to use or alternatives, but the prerequisite guidance is helpful.

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