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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether verification is read-only or mutating, not what auth or on-chain calls it performs, not rate limits, and not what happens on a failed check.

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 includes an unexplained internal identifier instead of substantive content front-loaded for selection.

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 five-required-parameter tool with no annotations, no output schema, and no parameter documentation, the description leaves an agent with essentially nothing needed to invoke it correctly.

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?

All five parameters (oracle_address, price_feed, reference_price, asset, tvl_at_risk) are required with 0% schema description coverage, and the description adds no meaning for any of them — notably reference_price units and tvl_at_risk usage are entirely undocumented.

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 a restatement of the tool name plus an opaque internal label: '[defi] Oracle guard (OGD-100-ManipulationBound)'. It hints at oracle price-manipulation protection but states no verb and no concrete action, so an agent cannot tell exactly what the tool does.

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 guidance on when to call this tool, when not to, or how it relates to siblings such as defi_risk_score, defi_liquidation_check, or defi_bridge_verify. The 'OGD-100' code provides no actionable routing information.

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