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

With no annotations, the description carries the full burden, and it conveys key behavior: newest-first ordering, the fields included per filing, and the date-filter semantics. It does not describe pagination or response envelope, but for a read-style listing tool the behavior is largely transparent.

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 sentences with no filler: the first front-loads the resource, ordering, and returned fields, and the second adds the filtering usage. Every clause contributes useful information.

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 low-complexity tool with two optional parameters and no output schema, the description covers the core return contents, ordering, and main filter. It could be more explicit about limit behavior or response shape, but the schema already provides reasonable defaults.

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 description explains `since` with format and intent, but the schema already provides the same after-date semantics. The `limit` parameter gets no description-level treatment beyond its schema default/max/min, and at 50% schema coverage the description doesn't fully compensate for that 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?

The description identifies a specific resource ('newest Periodic Transaction Reports'), a clear ordering ('newest first'), and enumerates the included fields such as buy/sell mix, tickers, and late-filing flag. This is a concrete verb-plus-resource statement that helps differentiate it from siblings like list_recent_filings.

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?

The description explicitly states the polling use case ('built for agents that poll') and explains when to pass `since` to get filings after a date. It does not explicitly mention when to prefer a sibling tool instead, so it stops short of full alternative guidance.

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