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

With no annotations, the description carries the full behavioral burden. It discloses the jurisdictions and data checked, but it does not state whether the operation is read-only, whether authentication or rate limits apply, how fresh the data is, or what the response shape looks like.

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 front-loaded and appropriately sized, moving from capabilities to usage to exclusions. It is somewhat repetitive, listing USPTO/EUIPO/UKIPO and active oppositions in both the first and second sentences, but there is no wasted preamble.

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 simple two-parameter lookup with fully documented schema fields, the description supplies enough scope and exclusion guidance to invoke it correctly. It is less complete on return format and matching behavior, which matters more because there is no output schema, but the core invocation context is present.

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 schema already documents both parameters, including the Nice class range and default. The description reinforces the brand-mark and Nice-classification concepts but adds no syntax, matching behavior, or other meaning beyond 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?

The description uses a specific verb and resource: checking trademark registrations, Nice classifications, active oppositions, and brand availability across USPTO, EUIPO, and UKIPO. It clearly distinguishes this tool from searchGlobalPatents and getDomainWhois, so an agent can select it without opening sibling schemas.

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?

It explicitly states when to use the tool: checking brand names, wordmarks, or slogans for live trademark conflicts, active oppositions, and Nice classification coverage. It also gives explicit exclusions and names the alternative tools for patents and domains, making the selection criteria unambiguous.

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