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

With readOnlyHint=true already communicating safety, the description adds meaningful context beyond the annotation: it specifies that results are grouped 'by strike' and that the metric reflects dealer hedging activity. This clarifies output granularity and interpretive framing, though it doesn't mention pagination or exact response structure.

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 exactly two sentences, front-loaded with the core action and followed by a useful output summary. Every word earns its place with no redundancy or filler.

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?

There is no output schema, and the description gives a high-level sense of the return content (net dealer delta, directional bias) but not its structure or units. It also fails to clarify that no strike parameter is required, leaving the 'by strike' phrase ambiguous in a tool with only symbol and expiration parameters.

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%, so the baseline is 3. The description's 'by strike' phrase could confuse an agent because there is no strike parameter in the schema, but it doesn't add any parameter-level detail beyond what the schema already provides. No compensation for the low-risk ambiguity is offered.

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 uses a specific verb ('Get') with a resource ('delta exposure (DEX)') and clarifies scope ('by strike'). It also names the key output ('net dealer delta and directional bias'), which clearly distinguishes it from sibling tools like get_gex (gamma exposure) and get_dealer_premium.

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?

The description implies usage for options-hedging analysis via 'from options hedging,' but it gives no explicit guidance on when to choose this tool over alternatives such as get_gex or get_dealer_premium. There are no exclusions or alternative recommendations, so only weak implied usage context exists.

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