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

Annotations already carry the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false). The description adds genuinely useful behavioral context: it is a bounded search over MRDS, returns specific fields, names the data source, and confirms no authentication is needed. No contradiction 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?

Three sentences with no filler: the first announces the operation and scope, the second summarizes the return payload and use case, the third gives source and auth status. Everything earns its place and key discriminators are front-loaded.

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?

For a read-only, idempotent bounding-box search, the description covers all essential call-time concerns: what it searches, what it returns, why you would use it, where the data comes from, and whether auth is needed. The output schema and annotations supply the remaining structural and safety details, so nothing an agent needs to invoke this correctly is missing.

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% and each parameter already has a clear description including ranges and the limit's default/max. The description adds the useful unifying concept of a 'geographic bounding box (min/max latitude and longitude)', which helps agents reason about the four coordinate parameters, but it does not add per-parameter details beyond what the schema provides.

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 starts with a specific verb ('Search'), a well-defined resource ('USGS Mineral Resources Data System (MRDS)'), and a crisp discriminator ('within a geographic bounding box'). It also enumerates what returned records contain, so an agent can immediately tell this from every sibling tool 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?

The description gives clear application context ('useful for regional mineral exploration and mapping') and states a practical requirement ('no auth required'). It stops short of explicitly naming alternatives or exclusions, but the bounding-box framing is enough to route an agent toward this tool for area-based deposit searches.

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