getAdvanceEarnProduct

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

No annotations are provided, so the description carries the burden. It discloses that no authentication is required and specifies a rate limit, which is useful for a query tool. However, it does not mention any potential side effects or other behavioral details.

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?

Description is extremely concise: two sentences covering purpose, authentication, and rate limit. It front-loads the core purpose immediately, with no wasted words.

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?

No output schema exists, and the description does not elaborate on the return format. While the purpose is clear, a query tool without output schema could benefit from hints about the response structure. However, the context signals (no nested objects, simple params) keep the tool relatively straightforward.

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 has 3 parameters (category, coin, duration) with 0% schema description coverage. The tool description adds no explanation of their meaning or format. This leaves the agent with insufficient information to correctly specify parameter values.

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?

Description states 'Query available Advance Earn product listings', which clearly identifies the verb ('Query') and the resource ('Advance Earn product listings'). The resource is specific and distinct from sibling tools like getEarnProduct or getFixedTermProduct.

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?

Description provides authentication and rate limit info ('No authentication required. Rate Limit: 50 req/s (IP)'), but lacks explicit guidance on when to use this tool over similar sibling tools like getEarnProduct or getTokenProduct. Context is partially implied by the name.

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