linkrisk

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

No annotations provided, so description must fully disclose behavior. It only lists checks without stating if the operation is read-only, the response time, or privacy implications. The term 'lightweight' hints at speed but lacks specificity.

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?

Single sentence after cost indicator, front-loaded with key information. Every word earns its place with no redundancy.

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?

No output schema, so description should indicate return value. It only lists what is checked but not the format of the risk profile (e.g., score, flags). Adequate for a simple tool but leaves some ambiguity.

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?

Only one parameter 'url' with no schema description. The description adds context that the URL is for risk checking, which is helpful but minimal. Baseline is 3 given low schema coverage, but it doesn't provide format or constraints.

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?

Description clearly states it produces a URL risk profile, listing specific checks (phishing, redirects, domain age, IP reputation), and distinguishes from siblings like 'linksafe' by focusing on risk profiling.

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?

Directly advises 'Use before visiting unknown URLs', providing a clear use case. However, it does not mention when not to use or explicitly differentiate from the sibling 'linksafe'.

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