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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only an internal guard label and does not disclose what is checked, what thresholds apply, or what happens on failure.

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 short, but it is under-specified rather than concise. A single bracketed fragment does not front-load the actionable information needed to select or invoke the tool.

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 verification tool requiring five inputs, with no output schema and no parameter descriptions, the definition is far too thin. It does not provide enough context for an agent to confidently select or invoke the tool.

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?

The tool has five required parameters — oracle_address, price_feed, reference_price, asset, and tvl_at_risk — with 0% schema description coverage. The description mentions none of them, so an agent must infer every parameter's meaning from the bare schema names.

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 only a category fragment, '[defi] Oracle guard (OGD-100-ManipulationBound)', and does not state a clear verb or resource such as verifying an oracle price feed. It gives no differentiation from the many nearby defi and verification siblings.

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 use this tool, when not to use it, or which sibling tools are alternatives. In a large toolset with defi_risk_score, defi_contract_audit, oracle_hallucination, and others, the agent receives no routing context.

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