Authorize Webapp

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

No annotations exist, so the description carries the full behavioral burden. It discloses important non-obvious traits: codes are single-use, expire after 5 minutes, and authentication is only completed in the browser once the user returns to the webapp. This is strong transparency for an authorization 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 single-sentence purpose statement is front-loaded, followed by a compact workflow explanation. No filler or redundant content; every sentence adds relevant operational detail, though the length is slightly more than minimal.

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 two-parameter tool with a full schema and output schema, the description covers the complete invocation flow: source of the code, required inputs, single-use/expiry constraint, and the required post-call user action. Minor details like error handling for invalid/expired codes are absent but acceptable given the tool's simplicity.

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 coverage is 100%, so baseline is 3. The description adds meaningful context beyond the schema by explaining where the code comes from, its exact message format, and that it must be paired with the user's Telegram chat id. This helps an agent correctly extract and pass parameters.

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 opens with a precise verb and resource: 'Authorize a browser on the Torrent Search webapp via its pairing code.' This clearly identifies the tool's action and distinguishes it from sibling tools like search, get, and forward, which have different purposes.

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 thoroughly explains when to use the tool: when a user sends an 'Authorize <CODE> for Torrent Search' message, with the code and chat id as inputs. It doesn't explicitly list alternative tools to use instead, but no siblings fulfill this same role, so exclusion is not necessary.

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