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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds value by clarifying that the output is circumstantial (not statutory proof) and by listing what the profile contains, which helps the agent interpret results. It doesn't mention performance, caching, or data sources, but with annotations covering the safety profile, this is adequate. No contradiction with 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 information-dense but well-structured: it leads with the core purpose and output components, then adds usage context and a caveat. Each sentence earns its place; nothing is wasted. It is slightly long but not bloated, and the most critical information (what the tool returns) is front-loaded. A 4 is warranted for its efficiency.

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 carries the full burden of explaining what the agent will receive. It enumerates all major components (fame tier, path, class footprint, portfolio size, crowding, TTAB history) and clarifies the evidential weight. It also provides usage context and the parameter behavior. For a tool of this complexity, the description is complete and leaves no critical gaps.

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% for the single parameter mark_or_stem, with a clear explanation that it accepts either a full mark or a brand stem. The description repeats this concept but does not add any new semantic detail beyond the schema. Since the schema fully documents the parameter, the baseline of 3 is appropriate.

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 verb ('Get') and a clearly defined resource ('full fame profile for a brand'), then enumerates the specific components returned (fame tier, path, class footprint, portfolio size, crowding, TTAB history). It explicitly distinguishes itself from the sibling is_mark_famous by implying this provides a detailed profile rather than a simple yes/no answer, and it adds a caveat about circumstantial vs statutory proof. The purpose is 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?

The description states concrete use cases: 'explain WHY a mark is (or is not) famous' and 'profile a senior mark before a §2(d) / opposition / dilution strategy.' It also warns that the output is 'circumstantial signal, not statutory fame proof,' which guides appropriate reliance. It does not explicitly name alternatives like is_mark_famous for quick fame checks, but the context makes the intended use clear. This is strong guidance, slightly short of naming when-not-to-use alternatives explicitly.

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