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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: filtering/counting only qualifying target marks, separately reporting all targets attached to qualifying proceedings, and a caveat that claimed-color metadata does not prove pleading allegations. This goes beyond the annotations without contradicting them.

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?

Three sentences, front-loaded with the primary action. Every sentence earns its place: main purpose, filtering/reporting behavior, and a caveat with alternative. No filler or redundant restatement of schema fields.

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 13 parameters and no output schema, the description gives a solid high-level picture of outputs: counts of filtered target marks and separate reporting of all targets. It covers key nuances (exact class-only, color caveat) and points to an alternative for deeper evidence. It does not detail all return fields, but for an analytic tool this is acceptable.

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 77%, so baseline is 3. The description adds value for target_class_match by explaining 'exact class-only questions,' and clarifies the limited evidentiary weight of color claims (relevant to target_claims_color and target_color_families). This compensates for the missing 23% and enriches parameter understanding.

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?

Description opens with a specific verb-resource combo: 'Analyze one trademark owner's TTAB enforcement in a single call.' It clearly distinguishes from siblings by emphasizing the single-call analysis and by pointing to analyze_ttab_proceeding for deeper color-evidence verification. The scope is unambiguous and not a tautology.

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?

Provides clear context for use: analyzing a single owner's TTAB enforcement, including class/type/color filters and exact class-only needs. It explicitly directs to analyze_ttab_proceeding when color evidence must be confirmed in pleadings, giving a specific alternative. It lacks broader 'when not to use' guidance but is sufficient for most scenarios.

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