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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context: the data source ('USPTO PatentsView synced data'), cost per call, and a concrete example of the returned rollup shape, which goes beyond the 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?

The description front-loads use cases and the core return statement, then supports them with a concrete example and source/cost details. It is slightly longer than strictly necessary, but every sentence carries 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?

For a tool with no output schema, the description gives a useful preview of results and even an illustrative example. However, it omits the role of the patent_year parameter, output shape, and any caveats about data freshness or coverage, leaving an agent with incomplete information for fully correct invocation.

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 0%, so the description must compensate. It clarifies assignee_name indirectly through 'by assignee', but patent_year is never explained — it is not mapped to output filtering or to the 'filing years' mentioned in the description. This leaves the optional parameter semantically opaque.

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 uses a specific verb and resource: 'Returns USPTO filing rollups by assignee' with concrete output dimensions (patent counts, filing years, CPC classification). The Qualcomm example makes the tool's capability vivid and unambiguous, and it is clearly distinct from any sibling tool.

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 explicitly names three trigger scenarios: assessing company IP portfolio strength, tracking competitor patent activity, and M&A patent due diligence. It does not name exclusions or alternative tools, so it stops short of full when-not guidance.

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