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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether this reads state, moves funds, or requires authorization. For a DeFi tool taking a principal amount, the absence of any statement about whether it executes or merely computes is a serious gap.

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?

It is short, but this is under-specification rather than conciseness — the single fragment is a codename, not a front-loaded statement of function, so it earns its brevity for the wrong reason.

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?

With no annotations, no output schema, and 0% parameter coverage, the description needed to supply purpose, behavior, and parameter meaning, and it supplies none of them.

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% for two required parameters. The description adds nothing about principal_usd units/bounds or what risk_tolerance's 0-1 float scale means, leaving both parameters undocumented in both schema and description.

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 is essentially the tool name restated as a tag plus codename: '[defi] Yield Oracle (YLD-100-YieldConvergence)'. 'Yield Oracle' hints at the DeFi yield domain, but there is no verb or statement of what the tool actually does — optimize, quote, verify, or aggregate yields. An agent cannot distinguish it from siblings like defi_optimize or defi_oracle_verify.

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 when-to-use guidance, no preconditions, no mention of alternatives such as defi_optimize or defi_risk_score. The agent is given nothing to route on.

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