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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond that: it only uses public USPTO owner resolution, only returns system-generated deadlines, and explicitly excludes workspace/client/reminder/user-created deadlines. This helps an agent understand data provenance and limitations without contradicting 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 is two sentences with no filler. The first sentence front-loads the core operation and scope; the second states the privacy/data-source limitations. Both sentences earn their place and the description remains highly scanable.

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?

The description, combined with the annotations, output schema, and 100% schema coverage, gives an agent everything needed to select and call the tool correctly. It clarifies data scope, exclusions, and the owner-level perspective without needing to repeat parameter or return-value details already present in structured fields.

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 all seven parameters are already documented in the schema. The description does not add parameter-specific detail, though the owner-scoping language reinforces the meaning of owner_name. This meets the baseline for a fully schema-documented tool.

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 and resource: get public, system-generated trademark deadlines for a specific owner's marks. The owner-level scope clearly differentiates it from firm- and mark-level siblings like get_firm_deadlines and get_mark_deadlines. It also explicitly disclaims workspace, client, reminder, and user-created data, making its scope unambiguous.

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?

Provides clear selection context by emphasizing public USPTO owner resolution and system-generated data, and explicitly says it does not expose workspace, client, reminder, or user-created deadline data. However, it does not name sibling alternatives outright or state explicit 'use this instead when...' guidance, leaving some inference to the agent.

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