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

Annotations only cover the safety profile (readOnly, idempotent, closed-world), while the description adds real behavioral substance: the returned fields, the two-tier candidate ranking rule, and an explicit disclaimer that candidates are not verified outcomes. That reliability caveat is exactly the kind of context annotations cannot carry.

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, followed by the ranking rule and disclaimer in dense but purposeful sentences. Slightly heavy; the identifier examples appear in both the description and the schema, which is mild redundancy.

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 values need not be explained, yet the description still summarizes what is returned and, more importantly, discloses the candidate-matching heuristic and its uncertainty. Nothing needed to call or interpret this tool 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 description coverage is 100% and the single parameter already documents the same example formats the description repeats. The description adds no syntax or matching-semantics detail beyond the schema, so the baseline 3 applies.

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+resource ('track an R&D project' with the patent linkage) and pins the domain to Indian public R&D projects. It is clearly separable from siblings like get_mineral_patents or verify_patent_provenance, which do not resolve a project record.

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 an explicit trigger ('Use this when the user asks about a specific Indian public R&D project') and enumerates accepted identifier forms (SATYABHAMA SNTMOM numbers, JNARDDC/S-58, title words). It does not state exclusions or name an alternative for the related-but-different patent queries, 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.