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

The description mentions 'Free, no key needed,' which goes beyond the readOnlyHint annotation by clarifying authentication requirements. It also notes 'snapshot-pinned' implying data versioning. No contradiction with annotations.

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?

Single, well-structured sentence that front-loads the action and includes essential details without any filler. Every word earns its place.

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?

For a zero-parameter listing tool, it fully describes what will be returned: bundle types, content, and key attributes. No output schema is needed given the simple nature, and the description is sufficient for an agent to understand the tool's role.

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?

Tool has zero parameters, so baseline is 4. The description adds context about what is included (sizes, vintages, download paths) but no further parameter explanation is needed.

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?

Clearly states it lists snapshot-pinned patent/innovation bundles with specific content (sizes, vintages, download paths). Distinguishes itself from siblings like get_ip_download_link, which likely fetches a specific link.

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?

Implies usage for browsing available bundles and notes that no key is needed, making it accessible. However, it doesn't explicitly contrast with alternatives like search or download tools, though the purpose is clear enough.

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