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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond them — that the endpoint is public and needs no API key — but says nothing about response shape, size or any rate limits on a public open-world call.

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 compact fragments, front-loaded with the resource and scope, with the access constraint last. Every clause carries information; only the missing verb slightly weakens the structure.

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?

With no output schema, the description carries the burden of saying what comes back, and it does enumerate the three content categories (assets, datasets, day range). It does not describe the response format or how venues are keyed, so it is adequate but not fully self-sufficient for a discovery call.

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 there is nothing to document and the baseline of 4 applies. The description correctly implies no filtering input is required or accepted.

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 precisely — a per-venue inventory of what the archive holds (assets, datasets, day range) — so an agent knows this is a metadata/discovery call rather than a backtest or strategy check. It lacks an explicit verb ('returns'/'lists'), which keeps it just short of a 5, but the content is unambiguous and clearly distinct from the sibling tools.

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 statement of when to call this versus backtest_capacity, backtest_quote, check_strategy or plans. 'Public, no key' is an access note, not routing guidance, so the agent must infer that this is the discovery step before using the other tools.

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