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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds substantial value beyond that: an explicit pricing model ($0.003 in USDC per successful call via x402 on Base/Solana/Arc) and that failed calls are not charged, plus the 25-30 item feed-depth limit. This is meaningful operational context not present in structured fields.

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?

Front-loaded with the purpose and covered agencies, then return fields, filters, feed depth, and pricing. Dense and mostly efficient, though the return-field enumeration ('Each: agency, feed, title...') is somewhat redundant given an output schema exists.

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 an output schema present, the description needn't explain return values, and annotations cover the read-only/open-world profile. It still conveys the regulator scope, filters, feed freshness limit, and payment model, making it complete enough for an agent to invoke correctly, with only the usage-vs-alternatives gap remaining.

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 description coverage is 100%, so the schema already documents all four parameters, establishing a baseline of 3. The description restates the filters (agency, words/q, days 1-90) but adds no syntax or format detail beyond the schema, and omits the limit parameter entirely, so it does not exceed the baseline.

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 states a specific resource (enforcement items from regulator feeds) and enumerates exactly which agencies are covered (SEC litigation/administrative proceedings, CFPB enforcement, FTC, DOJ press releases), which distinguishes it from siblings like sec_events, sec_filings, or recalls. An agent can tell what it returns without opening the schema.

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?

It lists the available filters (agency, q, days) and discloses that feeds hold only the latest 25-30 items each, implying a recency scope. However, it never states when to use this tool versus alternatives such as sec_events or violations, nor any exclusion conditions. Usage is implied rather than guided.

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