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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and a closed-world scope. The description adds no behavioral context about whether this moves funds, requires approvals, or returns only an allocation recommendation. It does not contradict the annotations, but it contributes almost nothing beyond them.

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 very short, but the brevity is under-specification rather than efficient conciseness. The single fragment is not front-loaded with actionable meaning and spends its only content on an internal codename.

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 two-required-parameter optimization tool with no output schema and no parameter descriptions, the definition is missing the information an agent needs to invoke it safely. The annotations provide safety hints, but they do not fill the purpose, usage, or parameter gaps.

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 says nothing about either parameter. It does not explain principal_usd denomination, risk_tolerance scale or acceptable range, or any constraints, so it fails to compensate for the missing schema descriptions.

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 a tag plus codename, 'Yield Oracle (YLD-100-YieldConvergence)', rather than a verb-and-resource statement. It does not explain that the tool optimizes DeFi yield, what it returns, or how it differs from siblings like defi_optimize or defi_risk_score.

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?

There is no when-to-use guidance and no comparison to alternatives. It does not say whether to call this instead of defi_optimize or defi_risk_score, nor what context makes it appropriate.

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