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

No annotations are provided, so the description carries the full burden. It usefully discloses that data is sourced from SEC EDGAR, every row links to its filing, and the data is free and CC BY 4.0. It does not disclose update cadence, whether the data is cached or live, or any rate-limit behavior, but for a simple list-like tool the disclosed traits are reasonably helpful.

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 description is brief and well-structured: a clear subject line, a short list of content categories, and a final sentence covering source, linking behavior, and licensing. Every sentence earns its place with no filler or redundancy.

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 single-optional-parameter list tool with no output schema, the description covers the data domain, specific agreement types, data source, row-level filing links, and licensing. It does not enumerate return fields beyond the link or state update frequency, but those are minor gaps for a straightforward retrieval tool.

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 input schema has one parameter, limit, and its description is already 100% complete, explaining max rows, default, ceiling, and response metadata. The tool description adds no additional meaning about the limit parameter, so the baseline of 3 is appropriate.

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 clearly identifies the resource: material agreements under SEC 8-K Item 1.01, with sponsorships, naming rights, and partnerships as examples. It does not state an explicit verb like 'retrieve' or 'list,' but the tool name and noun-phrase description make the action clear. The subject matter is distinct enough from the sibling tools, though it never names or contrasts them.

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 scope is implicit: use this when you need material agreements, SEC 8-K Item 1.01 disclosures, or sponsorship/naming-rights/partnership agreements. However, there is no explicit guidance about when not to use it or which alternative tool might be better, leaving the agent to infer fit from the sibling names.

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