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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds value by disclosing that 'Results are cached for 30 days' – a concrete behavioral trait not present in annotations. It also outlines the analytical scope, giving the agent expectations about the output's content. No behavioral contradictions.

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?

Two sentences, zero filler. The first sentence states the core purpose; the second lists covered content and caching behavior. It is front-loaded and every word earns its place.

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 simple single-parameter API, annotations that cover safety/idempotency, and the descriptive scope of the summary, the description is largely complete. It includes the prerequisite to search_by_owner and the caching detail. The lack of an output schema means return format isn't specified, but for a summary-generation tool, the content description is sufficient for correct invocation.

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%, so the baseline is 3. The main description does not add any parameter-specific meaning beyond what the schema already provides. The schema's parameter description is helpful (covers format and instructs to use search_by_owner), but the description itself contributes no additional semantic enrichment.

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-resource pair: 'Get an AI-generated strategic analysis of a trademark owner.' It explicitly distinguishes from sibling tools like get_mark_ai_summary by owner scope, and the listed content areas (brand protection philosophy, litigation posture, portfolio evolution, class distribution, future behavior) make the purpose unmistakable. This is far beyond 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?

The description gives clear context for when to use the tool: when an AI-driven strategic owner analysis is needed. The parameter description adds a strong prerequisite: 'Use search_by_owner first to find the correct normalized name.' It doesn't explicitly mention when not to use it or alternatives, but the context is unambiguous enough for an agent to select it correctly.

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