getEarnHourlyYieldHistory

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

With no annotations, the description must disclose behavioral traits. It indicates a read operation ('Query') and a range constraint. However, it fails to mention pagination (cursor/limit), response format, or any rate limits. This is insufficient for a tool with 6 parameters.

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 extremely concise, using two short sentences and a bullet point. It front-loads the core purpose. However, brevity comes at the cost of missing essential parameter details, which could be added without significantly increasing length.

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 6 parameters, 0% schema coverage, no output schema, and no annotations, the description is woefully incomplete. It lacks parameter semantics, pagination details, and output format. An AI agent would struggle to use this tool correctly without external knowledge.

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%, placing full burden on the description. The description does not explain any of the 6 parameters (category, productId, startTime, endTime, limit, cursor). It only implies date range limits but provides no format or units. Without this, an AI agent cannot correctly use the parameters.

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 the verb 'Query' and resource 'hourly yield details'. It also specifies the product type 'FlexibleSaving', which helps distinguish from sibling tools that may query other yield products or time granularities. However, 'details' is vague and could be more specific about what data is returned.

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 description explicitly limits usage to 'FlexibleSaving' and mentions a 'Maximum query range is 7 days', which provides clear usage constraints. However, it does not explicitly state when not to use this tool or provide alternatives among the many sibling yield-related tools.

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