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

With no annotations and no output schema, the description carries the full behavioral burden. It discloses useful traits: the 200-filing measurement window, that lag is measured from SEC acceptance time, and that the endpoint is free (no paid tier/auth gating). It never states read-only semantics, rate limits, or refresh cadence, so the safety profile is left to inference.

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 entire body is duplicated verbatim, doubling the length with zero added information — a clear structural defect. The lead '[Filings Oracle]' tag and the metric list are front-loaded well, but half the text is pure waste.

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?

There is no output schema, so the description must enumerate return values, and it does so thoroughly: poll recency, newest filing age, median and p95 lag, per-form-type poll status, and row counts. For a zero-parameter metrics endpoint that is nearly sufficient, with only read-only semantics and latency expectations left unstated.

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. Nothing in the schema needs compensation, and the description correctly describes a no-argument reporting endpoint rather than implying hidden filters.

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 exact resource and the specific measurements returned: seconds since last successful SEC poll, newest filing age, median/p95 ingest lag over the last 200 live filings, per-form-type last poll, and stored row count. A specific verb is absent (it reports rather than 'gets'), and it never names a sibling, but the freshness/diagnostics intent is unambiguous against the content-oriented filings_* siblings.

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?

'Proof of real-time' and the '- Free' tag imply the use case — auditing whether the SEC data pipeline is current before trusting other filings_* results — but no explicit when-to-use, exclusions, or alternatives are stated. Usage is inferable rather than prescribed.

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