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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds some scoping context ('bundled oracle feeds' and 'on-chain') but does not disclose what validation returns, whether it reads from a specific chain state, or any failure modes. No contradiction with annotations is present.

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 one compact, front-loaded sentence with no wasted words. 'Validate bundled oracle feeds on-chain' delivers the core action and context efficiently.

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?

The tool has an opaque raw-JSON parameter, no output schema, and no explanation of what 'validate' produces or expects. This makes correct invocation uncertain. The description is too sparse to be complete for an agent, especially with a large sibling list and no way to infer input or output expectations.

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 schema has high description coverage for the single 'params' field, but that field is an opaque raw JSON passthrough. The description references 'bundled oracle feeds', which hints at the intended payload, but it does not specify the structure, required keys, or how feeds should be encoded. Baseline 3 applies because the schema at least describes the param itself.

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 action ('Validate'), a specific resource ('bundled oracle feeds'), and the execution context ('on-chain'). It is clear and distinct from most siblings, though it does not explicitly distinguish itself from peer_oracle_supports_inline or other validation-related tools.

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 instead of alternatives, no mention of prerequisites, and no exclusions. The only implied usage is that it validates bundled oracle feeds, but it does not help an agent choose among the large sibling set.

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