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

No annotations exist, so the description carries the full burden. It does disclose pagination behavior and a valuable prompt-injection warning about *_untrusted/agent-authored fields, but says nothing about permissions, rate limits, ordering of results, or what a response looks like for a read tool with five undocumented parameters.

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 tight sentences with the operational statement front-loaded and no filler. The second sentence is somewhat generic boilerplate about Commons/*_untrusted content, but it is a substantive safety instruction rather than padding.

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 five undocumented parameters, no annotations, and no output schema, the description should define what a series record is, how filters combine, and what pagination returns. It instead covers only the reading action plus a security caveat, leaving core invocation semantics unaddressed.

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 all five parameters (limit, topic enum, cursor, source, series_key) are undocumented in the schema. The description only says 'filters and cursor pagination' and adds no meaning for topic, source, or series_key, nor any note about the 200-item limit — it does not compensate for the coverage gap.

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?

States a specific verb and resource ('Read actual recurring series facts') plus the retrieval mechanism ('filters and cursor pagination'), so the agent knows this is a filtered list operation. It does not distinguish itself from plausible siblings such as get_market_history or ledger_summary, and what a 'series' contains is left implicit.

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?

Usage is only implied by the mention of filters and pagination; there is no statement of when to prefer this over get_market_history, ledger_summary, or truth_recent. The 'absent facts remain unknown' line hints at a completeness caveat, which is a mild usage signal but not explicit routing guidance.

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