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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the description only needs to add context, and it does: primary-document provenance, verbatim quotes, and the tier note 'full history Pro (never a 403)' signals access limitations. It stops short of describing pagination or ordering behavior.

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?

Sectioned and front-loaded: identity first, then USE/DO NOT USE, then filters and citation. Dense and largely earning its place, though the field enumeration and citation instruction add mild bulk.

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?

No output schema exists, so describing each row's fields is valuable and the description does it. For an 8-parameter tool the missing date-range filter semantics are the main gap, but an agent can still call it correctly for the documented filters.

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 0%, so the description must compensate. It documents jurisdiction (with the full enum of values), agency, event_type, and limit, which is genuinely useful, but it never explains the to/from/since date parameters or the 'all' flag — four of eight parameters remain undifferentiated.

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 (dated log of semiconductor trade-policy actions) with concrete scope (export controls, entity listings, tariffs), the anchor source (government primary documents back to Oct 2022 BIS rule), and enumerates the row fields. It is clearly distinguishable from get_market_intelligence and other siblings.

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?

Explicit 'USE THIS for' with three concrete query examples and an explicit 'DO NOT USE for' that names the alternative (get_market_intelligence) plus a scope exclusion (rumored/anticipated actions are not recorded). This is exactly the routing an agent needs.

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