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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still adds the upstream source (USPTO Open Data Portal / data.uspto.gov) and the full shape of what comes back, including the junior/senior party structure. It says nothing about rate limits, pagination behavior, or auth requirements beyond the _apiKey parameter already in the schema.

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?

Front-loaded with the definition and the sibling-docket boundary, then filters, then returns. The enumerated return-field list is long but justified since there is no output schema; it is the one part that reads as padding against an otherwise tight definition.

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 no output schema, the description carries the return contract and does so thoroughly (interference number, style, declaration date, party details, decision type/date/outcome, document link). All seven parameters are optional and documented in the schema, and the data source is disclosed, so an agent has everything needed to invoke correctly.

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 description coverage is 100%, so the baseline is 3, but the description earns more: it clarifies that party matches junior- or senior-party name *or either party's real party in interest*, a distinction the schema omits, and that the filters combine with 'and/or'. patent_number's 'patent or application' semantics are largely already in 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?

States a specific verb+resource ('Search USPTO patent Interference decisions') and then defines the domain term — pre-AIA priority contests between competing applicants/patentees. It explicitly distinguishes this docket from AIA trials and ex parte Appeals, so an agent can tell it apart from ptab_search_decisions, ptab_search_appeals and ptab_search_proceedings without opening a schema.

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?

Clear context for when this tool applies: interference proceedings only, and the description names the filter dimensions (patent_number, party, query) that select within that scope. It signals the boundary against AIA trials and Appeals, but never names the sibling tool an agent should use instead for those dockets, so routing is implied rather than explicit.

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