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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them by disclosing output granularity: 'Mineral-level counts only, not record-level links,' which tells the agent not to expect per-record provenance.

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?

Four tight sentences, front-loaded with the trigger conditions, then the comparison semantics, then the granularity caveat, then the default. No filler or restatement of the title.

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 an output schema present and annotations covering safety, the description only needs to cover purpose, scope, granularity and the no-argument default – all of which it does. An agent has everything needed to call it correctly.

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 the mineral parameter's description enumerates all valid ids, so the schema does the heavy lifting (baseline 3). The description adds the default/omission semantics ('Omit mineral to compare all'), clarifying behavior the schema only implies via 'Optional'.

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 names a specific operation (comparing patent families against funded Ministry of Mines S&T projects) and a specific scope (each India-list critical mineral, mineral-level only), which cleanly separates it from siblings like get_mineral_patents and track_rd_project_ip.

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?

It gives concrete user-question triggers: 'where India's critical-mineral technology gaps are', 'which minerals have patents but little funded R&D (or the reverse)', and collaboration opportunities. It does not, however, name an alternative tool or state when not to use this one, 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.