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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond that: Mon/Thu 09:00 UTC refresh cadence, human-reviewed status changes, and the anonymous-caller truncation with a free-API-key path to full history. It also discloses the return shape (matrix rows with date/source URL/confidence) and citation requirements.

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?

Dense but front-loaded: the resource and return shape come first, then use/don't-use routing, then filters and auth. Nearly every sentence earns its place, though the citation string and API-key URL add some length that could be trimmed.

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 no output schema, the description compensates by explaining the two returned collections (matrix and timelines) and their fields, including the status-change progression. Auth requirements, refresh cadence, and truncation behavior are all covered, so an agent has everything needed to call and interpret it.

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 carry the burden, and it does list all four filters with meaning: vendor/geneneration enums by name, customer as substring match, and include_timelines tied to the timelines output. It stops short of stating defaults or whether filters are AND-combined, which keeps it just below a 5.

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 (HBM qualification tracker) with precise scope: which memory vendor passed which AI-accelerator customer's qualification, by generation and stack height. It names concrete enum values (SK Hynix/Samsung/Micron; HBM3/HBM3E/HBM4) that let an agent distinguish this from sibling tools 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?

Explicit 'USE THIS for' block with example queries and an explicit 'DO NOT USE for' block that names the two alternative siblings (get_hbm_market_data, get_accelerator_costs) along with the condition that selects each. Nothing is left to inference.

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