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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description does add genuine value by disclosing data provenance (GEX plus SEC FTD) and explicitly flagging that the FTD signal is a proxy for short-selling pressure rather than true short interest, which affects interpretation. It says nothing about score range, refresh cadence, or output shape, so it stops short of rich behavioral context.

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?

It is a single sentence with no filler, but it is dense with unexplained proprietary terms ('SqueezeOS', 'chain-derived GEX') that force the agent to parse rather than act. The caveat is useful but buried at the tail rather than front-loaded.

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?

With no output schema and only safety annotations, the description carries the burden of explaining what comes back, and it never states the score's scale, components, or return format. The provenance and proxy disclosure are the right kind of content, but an agent still does not know how to read or threshold the result.

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?

There is a single required parameter with 100% schema description coverage ('Stock ticker symbol'), so the schema already carries the semantics. The description adds no guidance on ticker format, exchange suffixes, or symbol validity, which is the baseline expectation at full coverage.

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 names a specific computed artifact (a squeeze-pressure score) and its two inputs (chain-derived GEX and SEC fails-to-deliver), which lets an agent tell it apart from generic regime or volatility siblings. The verb is implied by 'track' in the name rather than stated, and heavy proprietary jargon ('SqueezeOS FTD oracle') adds noise rather than clarity.

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 statement of when to use this tool versus alternatives such as track_volatility_surface, classify_microstructure_regime, or live_universe_scanner_scan. An agent must infer usage purely from the score's subject matter, and no prerequisites or exclusions are given.

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