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

Annotations cover readOnlyHint and openWorldHint, so the safety profile is set. The description adds meaningful behavior beyond that: the access-tier limitation (trial returns only ten latest items, paid tiers return the whole store) and the semantic decoding of the sign field (green opens, red tightens, grey informs). It does not mention pagination or ordering, but the added context is substantial.

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?

Three dense sentences organized as return content, then filters, then access tiers. Front-loaded with what the tool returns. Slightly packed but every clause carries information; no filler.

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 7-parameter, no-output-schema tool with low schema coverage, the description covers returned fields, most filter values, and access tiers. Missing: limit behavior and valid kind values, which an agent might need to call it optimally.

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 only 29%, so the description must compensate, and it does: it enumerates the jurisdiction enum values (sec, cftc, usbank, eu, uk, row, macro), gives the since format (YYYY-MM-DD), and explains the sign semantics. It does not document the limit parameter or list valid kind values, leaving some gaps.

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 (structured regulatory events) with named source categories (SEC, CFTC, US banking regulators, Treasury, EU, UK, RoW, macro) and the fields each event carries. An agent can distinguish this from siblings like get_news or get_crypto_regulation from the description alone.

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 filter list implies how to narrow results, and the tier note ('Trial: ten latest; ... the whole store') tells the agent about access constraints. However, there is no explicit when-to-use guidance or naming of alternative tools for regulatory vs. general news queries.

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