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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description adds genuinely useful behavioral context: the underlying data sources (SATYABHAMA Ministry of Mines S&T, JNARDDC projects) and the granularity limit ('mineral-level counts only, not record-level links'), which prevents wrong expectations about drill-down.

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 trigger, then data sources, then the granularity caveat and the default-scope note. Every sentence carries information, though the parenthetical source listing is slightly dense.

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?

An output schema exists, so return format needs no explanation. The description covers purpose, triggers, data provenance, scope/granularity, and the default-argument behavior — everything an agent needs 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 description coverage is 100% and the mineral id enumeration is already in the schema, so the baseline is 3. The description adds meaning beyond it by documenting the default behavior when mineral is omitted (compare all), which the schema does not state.

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 analytical verb+resource: comparing patent families against funded R&D projects per India-list critical mineral to surface technology gaps. It is clearly distinguishable from siblings like get_mineral_patents (patents only) and track_rd_project_ip by naming the gap-analysis output.

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?

Gives concrete user-intent triggers ('where are technology gaps', 'patents but little funded R&D or the reverse', 'collaboration opportunities') and explains the no-argument case ('Omit mineral to compare all'). It does not explicitly name which sibling to prefer or when to avoid this tool, 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.