getTokenDailyYield

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

No annotations are present, so the description must fully disclose behavior. It only adds a rate limit (10 req/s UID) but fails to mention that the tool is read-only, whether authentication is required, or details about pagination and response format. For a query tool with no output schema, this is insufficient.

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 brief and front-loaded with the purpose, followed by a separate rate limit note. It is concise, but could potentially include more parameter details without becoming overly long.

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 the tool has 5 parameters, no output schema, and required enum, the description lacks crucial context such as pagination behavior (implied by cursor/limit), date range semantics, and expected return format. The rate limit is useful but insufficient for 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?

Schema description coverage is 0%, and the description does not explain any parameter meanings beyond what the schema already provides. Parameters like startTime, endTime, and cursor are left without semantic context, despite being key for proper usage.

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 tool queries 'user's daily yield distribution records,' using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like getDistributionRecord or getTokenHourlyYield, which may have similar purposes.

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 guidance is provided on when to use this tool versus alternatives, such as getDistributionRecord or getTokenHourlyYield. The rate limit is mentioned but does not indicate appropriate usage contexts or exclusions.

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