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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description adds real behavioral detail beyond them: results are ordered newest filing first, and the response includes totals for the filtered set. It says nothing about rate limits or response size limits, keeping it from a 5.

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, front-loaded with what the tool returns and followed by filter/paging mechanics. The first sentence is a long comma-delimited field dump, which is informative but denser than necessary; still, every clause serves a purpose.

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 correctly compensates by enumerating returned fields and the presence of aggregate totals. Combined with 100% schema coverage for the six optional parameters, an agent has what it needs to call this correctly; only edge behaviors like empty-result handling are absent.

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 coverage is 100%, including enum values, patterns, and per-parameter examples, so the schema carries the load. The description only restates the filter axes at a high level and adds no format or syntax detail beyond what the schema already provides, matching the baseline 3.

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?

Names a specific verb and resource ('Delaware statutory trust offerings from SEC Form D filings') and enumerates the returned entity scope (issuer, offering size, first sale date, exemption, broker-dealers). An agent knows exactly what dataset this retrieves, and the sibling tools (exchange tax, deadlines) are so unrelated that no disambiguation is needed.

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?

Explicitly states the available filter axes and paging mechanism, so an agent knows how to narrow the query. It gives no when-not-to-use condition or alternative tool, but there is no plausible sibling alternative here, and the 'Filings data, not an offer or recommendation' line sets usage context.

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