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

With no annotations, the description carries the full burden, and it does disclose two genuine traits: the data is delayed by 30 minutes and it is a subset (sample) of the full paid dataset. It says nothing about rate limits, auth requirements, or refresh behavior, so the disclosure is partial rather than rich.

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 short fragments with the key differentiator ('Free') front-loaded, so it is appropriately sized and immediately scannable. The telegraphic style costs a little clarity, but nothing is wasted.

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 zero-parameter tool with no output schema, the description covers the essentials: cost, latency, and data scope. It remains thin on domain context, though, never explaining what 'positions' or 'events' mean in this API or how the sample differs in coverage from the paid feed.

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?

The tool takes zero parameters, so the baseline is 4 and there is no schema semantics for the description to extend or compensate for. Nothing in the description contradicts or misrepresents the empty parameter set.

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 resource content clearly: open positions and recent events, offered as a free sample of paid data. It implies a read operation without naming the verb, but an agent can tell what it returns. It only weakly differentiates from siblings like get_signals or get_history, since it never says how it relates to them.

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?

'Free' and 'a sample of the paid data' imply this is the fallback when the paid data is unavailable or unsubscribed, which is a real usage signal. However, no alternative tool is named and no condition or exclusion tells the agent when to prefer this over get_signals or get_history.

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