modifyEarnPosition

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

With no annotations, the description carries full burden. It mentions business rule restrictions, allowed/disallowed conditions, and an error code, but does not detail authentication requirements or side effects beyond the auto-reinvest flag.

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 concise with a main sentence and three bullet-point notes, front-loading the core purpose and efficiently adding critical constraints.

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?

For a tool with 4 parameters and no output schema, the description covers the main behavior and constraints but does not explain the return format or explicitly map autoReinvest values to actions, leaving some gaps for an AI agent.

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 0%, but the description explains the purpose of autoReinvest and requires category='OnChain'. However, productId and positionId are not described, and the meaning of '0'/'1' for autoReinvest is left implicit.

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 sets or unsets auto-reinvest for fixed-term OnChain positions, distinguishing it from other earn-related tools that handle different order types or position modifications.

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 states that only OnChain category is supported, flexible-term positions are not supported (with error code 180028), and provides constraints on when enabling/disabling is allowed, covering when to use and when not to use.

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