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

With no annotations, the description must carry the behavioral load. It usefully discloses the returned data shape (three forward-return horizons) and maps to an underlying REST endpoint, implying a read-only lookup, but it never states safety, ordering, freshness, or default result count behavior beyond what the schema implies.

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, front-loaded sentences with no filler; the payload contents come first and the constraining details follow. The endpoint mapping sentence is compact and earns its place, though the fragment style is a bit clipped.

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?

For a two-optional-parameter read tool with no output schema, the description adequately conveys what comes back and that filtering is optional. It omits return ordering, time window definitions for the returns, and any error or empty-result behavior, leaving an agent guessing about result shape.

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 both parameters are already documented with bounds and defaults. The description only restates that symbol filtering is optional, adding no format or semantics beyond the schema; 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?

The description names the resource (resolved Heat events) and the payload (24h/7d/30d forward returns), which is far more informative than the opaque tool name 'receipts' alone. It does not explicitly contrast itself with the siblings (asset, board, methodology), but the resolved-event/returns scope is distinct enough to route an agent.

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 only usage signal is that the symbol filter is optional and that limit bounds exist implicitly. There is no guidance on when to call this versus board or methodology, no prerequisites, and no statement of whether results are paginated or ordered.

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