screen_markScreen a brand name against the live trademark registers. Free, no account.
Returns every mark near it with a similarity tier, plus which registers were checked. This is the first thing to run when someone asks 'is my name taken'.
| Name | Required | Description | Default |
|---|---|---|---|
| mark | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable specifics: it returns every near mark with a similarity tier and which registers were checked, and it is free/no-account. It also clarifies the data comes from live registers, enhancing behavioral understanding 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 is concise with no filler. The first sentence front-loads the core action, followed by output details and usage guidance in just two short paragraphs. Every sentence earns its place.
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?
With no output schema, the description explains the return value (near marks, similarity tier, checked registers) and access requirements (free, no account). It also gives usage context. For a one-parameter read-only tool, this covers all necessary information.
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?
The schema has only 'mark' as a string with no description, and schema coverage is 0%. The description compensates by equating the parameter to a 'brand name', providing the necessary semantic meaning for the single simple parameter.
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 'Screen a brand name against the live trademark registers,' clearly identifying the verb (screen), resource (brand name), and scope (trademark registers). It also distinguishes this tool as the first step for checking name availability, setting it apart from sibling tools.
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 says 'This is the first thing to run when someone asks "is my name taken",' giving clear contextual usage. It does not name alternative tools, but the phrase 'first thing to run' implies a workflow context where other tools follow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct trademark research question: market activity, entity analysis, opposition deadlines, mark screening, and class suggestion. No two tools overlap in purpose, making selection unambiguous.
Tool names mix patterns: verb_noun (screen_mark, suggest_classes), noun_verb (holder_read), noun_noun (opposition_window), and gerund_noun (filing_landscape). While readable, the inconsistent structure makes the set feel less predictable.
Five tools is well-scoped for a trademark research domain. Each tool covers a major workflow step without redundancy or bloat.
The set covers the core trademark research lifecycle: class suggestion, mark screening, opposition deadlines, holder analysis, and filing landscape. No obvious dead ends for the stated purpose.