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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the comparison corpus (global database, 25+ jurisdictions). However, it says nothing about what the detection actually returns (patent list vs risk score vs radar analysis), latency, or cost, leaving the agent to guess at the output of a nominally 'risk detection' call.

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 purpose is front-loaded in the first sentence, with triggers and the fallback rule following in a logical order. The trigger enumeration is somewhat keyword-dense, but each phrase serves the disambiguation job rather than padding.

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 10-parameter tool with no output schema, the description covers purpose and triggers but never explains what a result looks like (patent matches, risk score, radar output) or which optional parameters materially change the analysis. The read-only annotations cover safety, but output shape remains an open 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?

Schema description coverage is 100%, so every parameter including queryMode, regions, patentStatus and enableRadar is already documented in the schema. The description adds nothing parameter-specific beyond the 25+ jurisdictions idea. Baseline 3 is the right ceiling when the schema carries all semantics.

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 first sentence gives a specific verb+resource+method: detect design patent infringement risk by comparing a product image against a global design patent database across 25+ jurisdictions. This clearly separates it from trademark/copyright siblings. It stops short of naming the closest sibling (utility patent detection or design similarity search), so the distinction still relies on the agent inferring 'design' vs 'utility'.

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?

It enumerates concrete trigger phrases (design patent detection, TRO case lookup, visual patent similarity) and adds an explicit fallback rule for when the user never says 'design patent'. It does not state when NOT to use it or point to a named alternative for adjacent cases such as utility patents or generic image similarity.

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