yields

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

With no annotations, the description must fully disclose behavior. It lists fields but fails to mention read-only nature, required permissions, data freshness, error handling, or rate limits. The behavior regarding the 'account' parameter (default empty) is unclear.

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 concise with two sentences. The first front-loads the core purpose, and the second lists details. No redundant information, though it could be more structured with parameter explanations.

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?

For a tool with 3 parameters and no output schema, the description lacks completeness. It doesn't describe return format, pagination, error cases, or response structure beyond field names. The default field set for each style could be clearer.

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 coverage is 0%, so description must explain parameters. The 'year' parameter is implied, 'monthly' is partially explained (monthly vs daily), but 'account' is not described at all. The description does not clarify the effect of the 'monthly' boolean or the default value behavior.

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 returns account return/value series for a year with monthly or daily styles, providing specific fields. It distinguishes from siblings like orders and accounts by being focused on yield data, though not explicitly differentiating from other analytical 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 usage guidance is provided. The description does not mention when to use this tool over alternatives, nor does it specify contexts where it should not be used, such as requiring specific account permissions or data ranges.

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