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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds substantial context beyond this: it is grounded in government primary documents, excludes rumored/anticipated actions, notes tiered access ('Latest slice for all tiers; full history Pro (never a 403)'), and explicitly lists the output row fields. No contradictions with annotations.

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?

Although the description is lengthy, it is well-organized with clear sections: definition, use cases, exclusions, filters, and access limitations. It is front-loaded with the core purpose and every sentence adds valuable operational information. There is no fluff or repetition of structured schema fields.

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?

There is no output schema, but the description fully compensates by enumerating every row field (jurisdiction, agency, event_type, title, dates, affected_entities, node_threshold, document reference, source URL, verbatim quote). It also covers fidelity, scope, filter hints, and access tiering, making the tool's behavior and results predictable for an agent.

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 has 0% description coverage and no enums, so the description must compensate. It explains jurisdiction (with enumerated allowed values), agency (with examples like BIS, USTR, MOFCOM), and event_type. However, it does not explain 'to', 'from', 'since', 'limit', or 'all' beyond their names, leaving some parameters under-specified. This is adequate but has clear 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?

The description opens with a specific, concrete definition: 'Trade-Policy Timeline — the dated log of semiconductor trade-policy actions...' anchored to primary documents. This clearly distinguishes it from siblings like get_market_intelligence and get_fab_events by focusing on government policy events, not analysis or fab-level events.

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 description provides explicit 'USE THIS for' and 'DO NOT USE for' guidance, naming the alternative tool (get_market_intelligence) and clarifying that only published actions are recorded. It also gives concrete example use cases, making it unmistakable when to invoke this tool.

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