add_links

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

With no annotations provided, the description carries the full burden of transparency. It discloses that autostart moves links to the download queue once resolved and mentions the priority range, but it omits important behaviors such as resolution side effects (network requests), error handling, and package handling.

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 description is concise, consisting of two sentences that are appropriately front-loaded with the primary action. It adds relevant detail (autostart behavior and priority range) without wasted words.

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 tool with 7 parameters, no annotations, and no output schema, a two-sentence description is inadequate. It lacks return value information, side effects, and parameter details, leaving much to be inferred by the agent.

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?

The description explains the autostart parameter (moves to download queue) and the priority range (HIGHEST..LOWEST), but it leaves urls, package, extract_password, download_password, and destination_folder unexplained. With 0% schema coverage, this is insufficient for a tool with seven 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 clearly states the action ('Add URLs') and the target ('linkgrabber'), distinguishing it from sibling tools like add_container and move_to_downloads. It also provides brief notes on autostart and priority, reinforcing the tool's specific role.

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?

No explicit guidance is given on when to use this tool over alternatives like add_container or force_start. The description implies usage by stating the tool adds URLs to the linkgrabber, but it does not mention when not to use it or provide alternative tool references.

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