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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return value ('returns a risk matrix plus avoidance guidance') but does not state whether the operation is read-only, requires specific permissions, has rate limits, or has side effects. This is a significant gap for an assessment tool.

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 a single, compact sentence that front-loads the primary action and outcome. It is efficient and free of unnecessary detail, though it could include a brief mention of key parameters or usage context without becoming verbose.

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?

The tool assesses multiple IP dimensions and has three parameters, but the description only addresses the required parameter and does not explain the optional ones. The existence of an output schema mitigates the need to describe return structure, but the input semantics are insufficiently covered, leaving an agent to guess how to properly invoke the tool.

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 0%, so the description must compensate for undocumented parameters. It only refers to 'product category' (the required parameter) but says nothing about the optional 'market' and 'product_type' parameters, leaving their meaning and usage entirely unexplained.

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 tool assesses infringement risk across four specific IP dimensions (trademark, patent, copyright, design) for a product category, using an action verb ('assess') and a specific resource ('infringement risk'). This distinguishes it from siblings like brand_conflict_screen (likely a narrower brand-name check) and trademark_application_guide (a how-to guide), making the purpose 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 implies usage for a product category but offers no explicit guidance on when to choose this tool over siblings or when to avoid it. There is no mention of alternatives or exclusions, leaving an agent to infer the appropriate context without sufficient direction.

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