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

Annotations already declare readOnly, idempotent, non-destructive and open-world, yet the description adds real behavioral context beyond them: filing latency ('days to months behind the trades'), an explicit absence of prices, the return methodology (set-point windows, SPY comparison, result_pts sign convention), a required Tiingo attribution, and a prompt-injection warning to treat quoted content as text. That is substantial disclosure the annotations do not carry.

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 definition is a single sprawling block that repeats itself (no prices is restated twice, disclaimers about advice and instructions pad the tail) and buries the core purpose under methodology and legal caveats. The field list is front-loaded, but the rest is not tightly structured.

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?

Since there is no output schema and no parameters, the description has to carry the whole return-shape explanation, and it does: field contents, return windows, sign convention, and data provenance. It is complete for this tool, if over-delivered in volume.

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 zero parameters and an empty schema, the baseline is 4; there is nothing for the description to clarify about inputs.

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 opening sentence names the verb and resource ('the strongest signals on Aeon right now') and enumerates the returned fields (ticker, dots, reasons, filings, latest_result), so an agent can tell this is a read of computed filing-derived signals. It does not, however, differentiate itself from siblings like search_filings or get_record, and the definition of a 'signal' only surfaces at the very end.

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 when-to-use, when-not-to-use, or alternative routing. The description says a signal is Aeon's own arithmetic published before outcomes are known, but never tells the agent to prefer this over search_filings, get_record, or get_ticker for a given request.

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