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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description adds free pricing, data provenance (SEC EDGAR public domain), and a verify-at-source/no-warranty disclaimer, but most of that is legal boilerplate rather than call behavior such as response shape or limits.

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?

Short overall, but 'Free.' and 'Price: free.' are redundant, and the sentence fragments read as disclaimer boilerplate rather than front-loaded purpose. Some trimming would help.

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 zero-parameter informational tool with no output schema and annotations covering safety, the description gives enough context to call it correctly and to know what content to expect (pricing, payment network, terms, data source).

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 there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% and empty by design.

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 resource (this server, tool prices, payment network, terms) and makes clear it is informational. It is easy to distinguish from the sibling data-fetch tools like get_8k_events, though the verb is implicit ('describes').

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?

Implied usage only: an agent can infer it is for learning about the server, pricing, and terms. There is no explicit when-to-use or when-not, and no guidance on calling it before other tools.

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