uspto_application_assignments

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), lowering the burden. The description adds slight behavioral context by listing the returned fields, but it does not disclose pagination, limits, ordering, or any caveats about assignment record availability.

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?

Two short, front-loaded sentences deliver the action and the key output fields without filler, repetition, or unnecessary detail. Every phrase contributes meaning.

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 one-parameter, read-only tool, the description is reasonably complete: it names the input and the main output fields. However, it omits the expected format of application_number and says nothing about response cardinality or ordering, and there is no output schema to compensate.

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% for the only required parameter, so the schema already documents application_number. The description adds no format, example, or further semantics for the parameter, which makes the baseline 3 appropriate.

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 verb and resource: 'Get assignment (ownership transfer) records for a patent application.' It also names the distinguishing output fields (conveyance type, assignor, assignee, dates), which separates it from siblings like uspto_application_details, uspto_application_continuity, and uspto_application_transactions.

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 implies the usage context: when assignment/ownership-transfer records are needed for a patent application. It does not explicitly name alternatives or state when not to use this tool, leaving the agent to infer routing from sibling names rather than receiving direct guidance.

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