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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes further by enumerating the three verdict states plus not_checked, and by noting that results carry match explanations and a per-register read timestamp, which tells the agent results can be stale rather than freshly queried.

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: purpose and scope first, then the return contract, with no filler. The second sentence is dense with enumerated states but every clause carries information an agent needs to interpret the result.

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?

There is no output schema, so the description must carry the return contract, and it does by naming all four verdict values and the accompanying mark/match/timestamp data. What remains unstated is whether unknown names land on no_live_match or not_checked and whether a lookup incurs latency, minor gaps for a four-parameter read-only 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 100%, so all four parameters (name, goods, classes, registers) are already documented in the schema, setting the baseline at 3. The description adds a genuine nuance through 'not_checked when no register in the check has been read yet', clarifying what a partial registers subset produces, but adds nothing about how goods maps to Nice classes beyond what the schema says.

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 gives a specific verb and resource ('Check whether a name is taken as a trademark') and names the exact jurisdictions covered (US, EU, Israeli registers). It does not distinguish itself from the sibling search_trademarks, so an agent gets a clear purpose but no explicit routing cue between the two.

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?

Usage is implied rather than stated: the tool answers 'is this name taken', which suggests pre-launch screening, but there is no explicit when-to-use or when-not-to-use guidance. The sibling search_trademarks is never mentioned, leaving the agent to infer which tool to reach for.

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