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

With no annotations, the description carries the full burden; 'Get ... summary' implies a read-only, non-destructive operation, which is reasonable but unstated. It does add real behavioral value by disclosing what the composite actually aggregates, which is beyond structured fields. Missing: cost/latency expectations, whether the summary is a score or a structured breakdown, and the two-provider minimum needed for any comparison to be meaningful.

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?

Two sentences, zero padding, with the core purpose front-loaded and the dimension list following as supporting detail. Every clause contributes either scope or content information.

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 3-parameter read tool with a fully documented schema and no output schema, the description supplies the one thing the schema cannot: what the composite summary contains. It falls short only on interpretation guidance (what a high HHI or weak manipulation-resistance result means) and on the fact that a cross-provider composite requires at least two providers to be analytically meaningful.

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% — symbol, providers, and period are all documented with bounds and examples in the schema itself. The description adds only the framing 'across selected oracle providers', which restates the providers parameter without extra semantics such as how provider mix affects the aggregate.

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?

States a specific verb and resource: a composite risk summary for an asset across selected oracle providers, then enumerates the six dimensions it aggregates (HHI, volatility, correlation, freshness, manipulation resistance, shared-dependency). That enumeration implicitly differentiates it from single-dimension siblings like get_correlation or get_feed_freshness, though it never names a sibling explicitly.

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 choose this over get_oracle_health, get_protocol_oracle_exposure, compare_oracle_deviation, or pre_trade_safety_check, all of which overlap in domain. 'Across selected oracle providers' hints that it is multi-provider comparative analysis rather than a single-feed check, but the agent must infer this.

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