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

With no annotations provided, the description carries the full burden of disclosing behavior. It clearly describes pagination (cursor-based up to 1000/page), ordering, filtering, and output fields. It does not explicitly state read-only or idempotent behavior, but the query nature is evident. The inclusion of attribution and pricing adds useful context.

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?

The description is concise (a few sentences), front-loaded with the core purpose, and uses efficient language. Every sentence adds value, including the closing note on attribution and pricing.

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?

Without an output schema, the description fully explains what each row contains (assignee, grant count, CPC areas, window, inventor count, first-time flag, attribution). It covers all key aspects: pagination, filtering, ordering, and pricing. The tool's complexity is well-addressed.

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% with detailed parameter descriptions and examples. The description lists the categories of filters (state, CPC, etc.) but adds no new semantics beyond the schema. The baseline of 3 is appropriate since the schema already provides full parameter documentation.

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?

The description clearly states the tool's purpose: identifying companies with clusters of patents via a bulk feed of granted-patent assignees ordered by grant count. The verb 'feed' and resource 'granted-patent assignees' are specific, and the mention of R&D/growth signal distinguishes it from sibling tools like uspto_assignees_search and uspto_patents_search.

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?

The description provides clear context for use (finding assignee clusters for growth signals) and lists available filters (state, min grants, CPC, etc.). However, it does not explicitly state when not to use this tool or suggest specific alternatives among siblings, though the bulk-feed nature implies it differs from search tools.

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