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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds genuinely useful behavioral context beyond the annotations: the returned patent families are candidates on shared minerals only, and are explicitly not verified project outcomes. It does not discuss pagination or result limits, which the output schema presumably covers.

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 compact sentences: trigger first, then what is returned, then the important limiting caveat. No filler, and the most decision-relevant information (when to call it) is 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?

With an output schema present, the description need not enumerate return fields, and it covers the essentials for a one-parameter read-only tool plus a meaningful caveat about candidate patents. It is complete enough to call correctly, with only minor room for noting result scope or limits.

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% for the single parameter, so the schema already documents that it accepts a project number or title words. The description's example (SNTMOM/...) and trigger phrasing mirror the schema rather than extending it, which is the baseline-3 case.

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: tracking a Ministry of Mines funded R&D project and the patents tied to the same minerals. It clearly separates the project-centric lookup (project number or title words) from a pure patent lookup. It does not explicitly name a sibling such as get_mineral_patents, so it falls short of a 5.

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?

"Use this when the user asks about a specific Ministry of Mines funded R&D project (an SNTMOM/... number or words from its title)" gives a concrete trigger, including the input forms that activate it. No explicit when-not or named alternative is provided, 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.