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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description correctly aligns with a read-only analysis tool. It goes further by disclosing an important data limitation: claimed-color metadata identifies candidates but does not prove color was alleged in the pleading, and it explains that qualifying filters apply only to target marks while all attached targets are reported separately.

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?

Four sentences cover purpose, core filtering behavior, an edge-case usage, and a critical caveat with no wasted words. The most important identity statement is front-loaded, and each subsequent sentence adds distinct information rather than restating the schema.

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 tool with 13 parameters, this description covers the essential analytical behavior, a key invocation pattern, and the most likely misinterpretation. The lack of an output schema means some return-shape ambiguity remains, but the description's focus on counts and separately reported targets mitigates that gap.

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?

With 77% schema coverage, the schema handles most parameter meaning, but the description adds value beyond it: target_class_match=only is tied to exact class-only questions, and the claimed-color fields are clarified as metadata-based rather than proof of pleading allegations. This helps an agent interpret the color and class parameters correctly without repeating the full 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 opens with a specific verb and resource: 'Analyze one trademark owner's TTAB enforcement in a single call.' It then clarifies the tool's distinct filtering-and-counting behavior and explicitly names analyze_ttab_proceeding as the sibling to use when color allegations must be proven, distinguishing this tool from an obvious 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 gives clear context for the tool's analytical role and explicitly routes color-evidence questions to analyze_ttab_proceeding. It also calls out the exact-class-only use case via target_class_match=only, but it does not contrast this tool with get_owner_ttab_stats or other enforcement-related siblings, so the guidance is useful but not exhaustive.

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