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

No annotations are provided, so the description carries the full behavioral burden. It discloses the data returned (snapshot, heat series, events with receipts) and implies read-only behavior via the GET endpoint reference, but it omits permissions, rate limits, and side-effect details. This is moderate disclosure without full annotation coverage.

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?

Two sentences, front-loaded with the core purpose and return contents, followed by an endpoint comparison. Every sentence earns its place with no wasted words.

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 simple one-parameter retrieval tool with no output schema, the description sufficiently explains what data is returned and provides an API reference. It leaves a minor gap in usage guidance versus siblings, but otherwise complete.

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%, with the single required parameter 'symbol' fully documented in the schema (ticker symbol, e.g. BTC or GME). The description adds no parameter semantics beyond the schema, so the baseline score of 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 states the tool returns one asset's detailed data: latest snapshot, 7d heat series, open event, and past events with receipts. It distinguishes itself from siblings like board and methodology by focusing on a single asset, and references the concrete endpoint GET /api/asset/{symbol}. It lacks an explicit verb, but the resource and scope are clear.

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 explicit guidance on when to use this tool versus siblings such as board, methodology, or receipts. The phrase 'One asset in depth' implies a single-asset focus, but it does not state when that is preferable to alternatives or any preconditions.

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