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

No annotations are provided, so the description carries the full burden. It adds a critical behavioral note: the data is a 2011 historical snapshot and instructs the user to use as_of in the response meta. This is beyond what the schema conveys. It does not cover all behaviors (e.g., pagination or response structure), but the caveat is substantive.

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?

The description is two sentences: the first front-loads the resource and scope, the second provides a necessary historical caveat. It is efficient with no fluff, earning a high score for conciseness and structure.

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?

Given 9 parameters, no output schema, and no annotations, the description provides sufficient context for basic use: data source, focus, and a key caveat about data age. It lacks explicit return value details, but the schema covers parameters and the description hints at response meta.

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 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond mentioning 'semiconductor-critical materials,' which hints at commodity/min_score but is not explicit. The schema already describes each parameter adequately.

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 clearly states the tool's purpose: searching USGS MRDS mineral deposit records for semiconductor-critical materials, with a specific count of 1,233 deposits. It is specific and easily distinguishable from the unrelated sibling tools (e.g., quantum funding, trade flows).

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 domain is clearly mineral deposits, and the sibling tools are unrelated, making the context obvious. However, there are no explicit when-to-use vs. alternatives or exclusions, though the description's focus on semiconductor-critical materials implies the intended use case.

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