fomo_get_snapshot_by_id

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hints at a read-like operation ('PnL/equity') but does not state safety, permissions, side effects, whether a user must own the snapshot, or what happens if the snapshot does not exist.

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 description is only a few words and wastes no space. However, it is closer to a compressed title than a full instruction, and the brevity comes at the cost of missing essential usage and behavioral context.

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 tool with two required parameters, no output schema, zero schema description coverage, and no annotations, the description is too sparse to let an agent correctly understand the input relationship, expected output shape, or when the tool applies.

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 0%, so the description must compensate. It uses 'snapshot id' which maps to snapshotId, but it ignores userId entirely and adds no meaning about how the two parameters relate, what types carry, or how the snapshot is identified.

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 that the tool returns PnL/equity for a given snapshot ID, and 'one snapshot id' differentiates it from the series counterpart. It clearly names the resource and result, even without an explicit verb.

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 guidance about when to call this tool versus alternatives. The sibling fomo_get_pnl_equity_series exists and is contextually related, but the description never mentions it or explains when a single-snapshot lookup is appropriate.

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