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

Beyond the annotations (readOnlyHint, openWorldHint, etc.), the description discloses a crucial behavioral caveat: recorded assignments are 'notice of a submitted instrument—not a legal opinion on present title, validity, scope, liens, or chain-of-title completeness.' It also names the specific endpoint source, adding transparency about data provenance and limitations.

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 two sentences: the first states purpose and return fields, the second adds a necessary interpretive caveat. Every sentence earns its place with no repetition or fluff, and it is front-loaded with the most important 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?

Given the simple one-required-parameter tool, the presence of a full output schema, and complete annotations, the description covers all necessary information: what it does, what it returns, and critical limitations. No gaps remain for effective use.

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 clear descriptions for _apiKey and application_number. The description does not add parameter-specific meanings beyond the schema, but it does reinforce the 'one patent application' context. This meets the baseline for well-documented 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 opens with 'Retrieve USPTO-recorded assignment/conveyance history for one patent application', which is a specific verb, resource, and scope. It lists the exact data returned (assignors, assignees, dates, conveyance text, reel/frame), clearly distinguishing it from siblings like get_patent or search_patents.

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 clearly states it is for retrieving assignment history for a single patent application, implying the appropriate context. However, it does not explicitly mention alternative tools or when not to use it, missing the opportunity to contrast with sibling tools like validate_claim or search_patents.

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