legal_fetch_patent_citations

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

Describes read-only, no side effects, idempotent, verified source (EPO OPS), and 24-hour cache. No annotations present so description carries full burden; lacks mention of rate limits or maximum citation count but otherwise thorough.

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?

Well-organized and front-loaded with purpose, then params, usage, source, cache, and feedback instruction. Slightly verbose but every sentence adds value.

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?

Covers purpose, input semantics, usage context, source verification, caching, and fallback feedback mechanism. Output schema exists so return values are not needed in description.

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 0%, but description fully compensates with detailed meanings, formats, examples (EP, US, CN, etc.), optionality, and normalization behavior for both parameters.

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?

Explicitly states it fetches forward and backward citation chains for a specific patent. Clearly distinguished from sibling tools like legal_search_patents_by_keyword and legal_fetch_patent_by_number.

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?

Provides explicit when-to-use (building a prior art chain for a known patent) and when-not-to-use (finding patents by topic), with a specific alternative named (legal_search_patents_by_keyword).

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