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

Annotations only declare readOnlyHint=true, so the description usefully adds the return contents (gross/net contributions, dominant expiry, units, data quality) and the exact-strike matching behavior. It does not cover rate limits or auth needs, but it adds real value beyond the annotation.

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?

Three short sentences, each earning its place: purpose, return shape, and the key non-behavior. The purpose and the exact-strike constraint are front-loaded with no 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, but the description enumerates what is returned and states the exact-strike constraint, which is adequate for a simple read-only attribution tool. Minor gaps around auth (apiKey vs OAuth) and any sibling relationship remain.

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 strike, symbol, and apiKey are already documented in the schema. The description reinforces the 'exact listed strike' constraint but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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: attributing gamma concentration at one exact SPY/QQQ strike to its expiries. The scope (exact listed strike, SPY/QQQ) is concrete, though it does not name a sibling tool to contrast with, so it falls just short of the top band.

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 line 'Does not silently choose a nearby strike' implies the caller must supply an exact listed strike, which is useful usage context. However, there is no explicit when-to-use-vs-alternatives guidance relative to the many other gamma/exposure siblings, leaving the choice largely to inference.

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