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

With readOnlyHint=true already covering safety, the description adds useful behavioral context: results are newest first, the total count comes from total_on_file, and the dataset is explicitly a USPTO strategic-area sample rather than every patent. It does not detail rate limits or authentication, but the sample caveat is important.

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 front-loaded with the resource and returned fields, then moves to invocation guidance and a caveat. It is somewhat dense but every sentence contributes useful information.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does: patent number, owner as filed, grant date, abstract, USPTO link, total count, and newest-first ordering. It also discloses the key dataset limitation.

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%, so the schema already documents all four parameters, including limit defaults and ranges. The description adds exact-match semantics for assignee and mentions offset paging, but does not add much beyond the schema.

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 states a specific resource and scope: patents HillSignal holds for a company, including the returned fields and ordering. It is clearly distinguishable from the sibling tools, none of which cover patent records.

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?

It gives concrete invocation guidance: pass ticker or assignee, use total_on_file for count questions, and use offset paging to list results. It does not name alternatives, but no sibling tool is a comparable patent lookup.

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