placeEarnOrder

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

With no annotations, the description carries full burden. It discloses delays during peak lending, non-cancellable redemptions, and longer OnChain processing. However, it misses auth requirements, rate limits, and other behavioral traits.

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 short, with two sentences and bulleted notes. The purpose is front-loaded. Each sentence adds value, though parameter details are missing.

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 10 parameters, 7 required, a nested object, and no output schema, the description lacks essential context. It does not explain parameter usage, return values, or prerequisites, making it inadequate for a complex tool.

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 description coverage is 0%, and the description provides no meaning for any of the 10 parameters. The tool name and summary do not explain what parameters like 'productId', 'redeemPositionId', or 'interestCard' are for.

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 'Place a Stake or Redeem order', specifying the verb and resource. It distinguishes the tool's action from siblings like executeLPStake or placeFixedTermOrder, though it doesn't explicitly differentiate from similar earn order tools.

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?

No explicit guidance on when to use this tool vs alternatives. The notes mention delays and cancellation restrictions, which are behavioral, but do not help an agent choose between this and sibling tools like placeAdvanceEarnOrder or executeLPStake.

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