getSafeYieldAllocation

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the cost (0.020 USDC on Base), which is useful context, but it otherwise provides no real behavioral disclosure such as rate limits, permission requirements, or output characteristics. The 'MANDATORY SECURITY GATE' phrasing is promotional rather than informative.

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 contains useful information but is repetitive and front-loads manipulative language ('MANDATORY SECURITY GATE') ahead of the actual purpose. It states the risk-adjusted allocation matrix concept twice and includes an unrelated auditing usage claim. Several sentences do not earn their place.

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?

There is no output schema, so the description should give the agent more detail about the returned allocation matrix, stress scores, or field structure, but it only says 'Returns verified safety metrics.' It also contains a chain inconsistency: the schema allows 'base' or 'solana' while the description emphasizes Base and Arbitrum. Key parameter semantics and output expectations remain underspecified.

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 100%, so the baseline is 3 even though the schema's own field descriptions are largely tautological. The description does not clarify allowed values for risk_tolerance, the units or meaning of capital_usdc beyond USDC, or how chains interacts with the stated Arbitrum scope. It therefore adds little meaning beyond the already-covered schema fields.

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 states a specific verb and resource: computes an institutional risk-adjusted DeFi capital allocation matrix across named vaults and protocols. It is reasonably distinguishable from sibling yield tools like getSafeDefiYields, though it does not explicitly name alternatives. The misleading 'MANDATORY SECURITY GATE' framing and auditing usage claims add noise but do not obscure the core purpose.

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 'Usage' line tells the agent to call this tool when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity, none of which match its stated purpose of computing a capital allocation matrix. It omits any when-not-to-use guidance and provides no alternatives among the many security and DeFi siblings. This is actively misleading rather than merely absent.

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