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

Goes well beyond the readOnly/idempotent annotations: it discloses the 5-calendar-year coverage window and that full history back to 2000 is not loaded, the upstream source (MSHA bulk mine-records, public domain), the weekly refresh cadence, and that no API key is required. These are exactly the constraints that would otherwise cause an agent to over-trust a sparse result.

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 primary action and a dense field inventory in one sentence. The parenthetical '(the response says so)' and the switcheroo from plural 'Violations/inspections/production' to singular 'is not loaded' are slightly clumsy but cost little.

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 carries the return-value burden and does list the major sections plus the flags and dates inside violations. It does not say what happens when a limit is exceeded (truncation vs. error) or what an unknown/retired Mine ID yields, which are the remaining gaps for a lookup tool.

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 100%, so mine_id and the two limit parameters are already documented. The description adds only the interpretive point that 'recent' means the last 5 calendar years, which bounds what the limits can return; it adds no syntax or default details beyond the schema. Baseline 3 fits.

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 verb and resource ('Look up a known MSHA Mine ID') and enumerates exactly what comes back: status, type, commodity, operator/controller, inspections, violations with penalties and S&S flags, and quarterly employment/production. The phrase 'known MSHA Mine ID' cleanly separates it from the sibling search tool that finds IDs from names.

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 qualifier 'known MSHA Mine ID' implies the prerequisite (you must already have an ID), and the schema points to msha_mine_search for name-based lookup. There is no explicit when-not-to-use or stated alternative in the description body itself, so it stops short of a 5.

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