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

Annotations already signal read-only and non-destructive behavior. The description adds valuable behavioral context by framing the output as 'circumstantial signal, not statutory fame proof' and detailing the kind of data returned (fame tier, path, etc.), helping the agent understand the nature and limits of the response beyond the safety 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 somewhat long but well-organized, front-loading the core function, followed by a structured list of returned attributes and then usage guidance. The length is justified by the complexity of a fame profile, but a few redundancies (e.g., 'brand' and 'mark wording') could be tightened.

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 tool's complexity and the absence of an output schema, the description thoroughly covers what data will be returned (fame tier, path, footprint, portfolio size, crowding, TTAB history), how to invoke it (by mark or stem), and a critical limitation (circumstantial, not statutory proof). This makes it highly complete for an agent to understand the tool's scope.

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 sole parameter mark_or_stem has a detailed schema description (100% coverage) explaining that a mark or bare brand stem resolves to the same family. The tool description only briefly repeats this ('by mark wording or brand stem') without adding substantial new meaning, so the schema carries the semantic burden.

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 clearly states the verb ('Get') and specific resource ('full fame profile for a brand'), enumerating the profile's components (fame tier, path, class footprint, portfolio size, brand-stem crowding, TTAB history). This distinguishes it from sibling tools like is_mark_famous, which presumably only returns a yes/no fame determination.

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?

Explicit use cases are provided: 'explain WHY a mark is (or is not) famous' and 'profile a senior mark before a §2(d) / opposition / dilution strategy.' The caveat 'Circumstantial signal, not statutory fame proof' serves as a when-not-to-rely-on guidance. However, it does not explicitly name alternative tools, such as is_mark_famous, for simpler fame checks.

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