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

Annotations already indicate this is read-only, idempotent, and non-destructive; the description adds substantial behavioral context by explaining the market-specific fame test, the class-as-market proxy, and the legal caveat that fame is not universal. It also discloses important output semantics such as is_famous, famous_in_class, fame tier, portfolio size, and TTAB plaintiff history.

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 with the core action and then systematically covers return fields, legal relevance, and an important caveat. The legal citation is dense but earns its place by preventing the common assumption that fame is class-agnostic. There is no filler.

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 compensates by listing the major return signals and framing their legal significance. The optional class behavior is already covered in the schema, and the caveat addresses interpretation risk. An agent has enough information to select and invoke this tool correctly.

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%, so the schema already documents both parameters. The description adds value by framing the class parameter as a proxy for the relevant market and explaining why fame is market-specific, which helps the agent decide when to supply or omit the class. It does not add much beyond the schema for the mark 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 opens with a specific action ('Checks whether a trademark is famous') and a clear resource, then adds market-specific nuance and the main return values. It is distinguishable from sibling fame/profile tools by its focus on fame tier, class-specific fame, and portfolio/TTAB context, though it does not explicitly name a sibling alternative.

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 provides clear legal contexts for use: likelihood-of-confusion strength under Section 2(d), dilution eligibility under Section 43(c), and general fame assessment. It also warns that the result is 'a circumstantial signal, not proof of statutory fame,' but it does not name alternatives or state explicit when-not-to-use conditions.

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