Product URL

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds real behavioral context beyond them: no request is sent, and Torob redirects the result to the canonical page carrying the product name. That is meaningful for deciding how to present the output.

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 short sentences, both front-loaded with substance: the first defines the operation and inputs, the second defines the use case and result behavior. Nothing is redundant.

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 one-parameter, no-output-schema utility, the description covers input forms, side-effect profile (no request) and the user-facing result (redirect to canonical page). Nothing an agent needs in order to call it correctly is missing.

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 single 'product' parameter is already fully documented. The description's list of accepted input shapes mirrors the schema rather than adding format or validity rules, so it earns the baseline 3.

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 operation (build/clean a torob.com product URL) on a specific resource (product), and identifies the three accepted input forms. The note that 'no request is sent' sharply distinguishes it from request-performing siblings like tb_product or tb_search.

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?

'Use to hand the user a link' gives a clear use context that an agent can act on, and the accompanying redirect note explains what the user will see. It stops short of naming an explicit alternative or a when-not condition, so it is context without exclusions.

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