fetchHedges

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

The description adds no behavioral details beyond what annotations already provide (readOnlyHint=true). It does not disclose any traits like data freshness, pagination, or authentication requirements.

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 extremely concise but at the expense of substance. For a tool with 14 parameters, a one-phrase description is not appropriately sized; it should front-load key usage 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?

Given the complexity (14 parameters, 31 sibling tools, no output schema), the description is severely incomplete. It fails to explain functionality, parameter roles, or expected outputs, leaving the agent with insufficient guidance.

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?

With 57% schema description coverage, the description does not add any parameter-level explanations. It misses an opportunity to clarify parameters like 'relation', 'minConfidence', or 'minDifference' that are crucial for finding hedging opportunities.

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 'Find Hedging Opportunities' is not a tautology and indicates a clear resource ('Hedging Opportunities'), but it is vague about what constitutes a hedging opportunity and how it differs from siblings like fetchArbitrage or fetchRelatedMarkets.

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?

No guidance is provided on when to use this tool, when not to, or how it compares to alternatives. The single phrase offers no context for selection.

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