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

No annotations exist, so the description carries the full burden, and it does substantial work: it warns that `count` equals limit and is NOT the conflict count, that judgments should use `has_conflicts`/`conflict_count`, and that a false `coverage.clearance_ok` means 'no conflict' is not clearance. It omits auth/permission and rate-limit behavior, but the interpretation caveats are exactly the kind of non-obvious behavior an agent needs.

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?

Front-loaded with the purpose, then parameters, then the critical interpretation warnings. The warning block is long but each line is load-bearing; the trailing return-shape list is somewhat redundant filler given no output schema exists.

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?

With no annotations and no output schema, the description supplies both the safety/interpretation context and an inline sketch of the return object (query, conflict_count, has_conflicts, count, results, coverage). Only the undocumented `country` parameter and absent sibling routing keep it from being fully complete.

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, and it documents query (with an example), nice_class (with an example and its effect on risk re-ranking), live_only (meaning and default) and limit (default). It leaves the `country` parameter (default 'US') undocumented, which is the one clear gap for a 5-parameter tool.

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?

States a specific verb and resource (search US trademark registry for conflicting marks by sound/form/meaning similarity) and adds the practical framing of checking a brand name before launch. It never names or contrasts with siblings such as graphic_trademark_search or trademark_lookup_by_serial, so the differentiation is implied by the tool name rather than stated.

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?

Explicitly says when to use it: before a seller names a product, to check for conflict with registered marks. It gives no exclusions or named alternatives (e.g. when to prefer graphic_trademark_search), but the context is unambiguous.

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