getEarnProduct

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

The description discloses that no authentication is needed, which is transparent. However, it does not mention other behavioral traits such as rate limits, data freshness, or idempotency. Given the lack of annotations, more disclosure would be beneficial.

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 consists of two concise sentences. The first states the core function, and the second adds the important auth requirement. No unnecessary information.

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 description covers the tool's purpose and auth, but lacks details about return structure, pagination, or filtering behavior. With no output schema, additional context about the response would improve completeness.

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?

The description does not explain the meaning or expected values of the input parameters ('category' and 'coin'). With 0% schema coverage, the description should compensate, but it instead focuses on output fields.

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 that the tool queries earn product information, listing specific output fields (APR, stake amounts, status). This distinguishes it from related sibling tools like getAdvanceEarnProduct or getFixedTermProduct, though it does not explicitly differentiate them.

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 only guideline provided is 'No authentication required.' There is no advice on when to use this tool versus alternatives, nor any prerequisites or typical scenarios.

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