linkfetch_safety_limits

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

With no annotations, the description carries the full burden, and it does disclose the informational, reference nature of the tool (published limits plus the reasoning behind them) which implies a non-mutating read. It never explicitly states that it is side-effect free or whether the values are static documentation versus live account state. For a zero-parameter reference tool the residual risk is low, hence 4 rather than 3.

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 with zero padding. The content summary is front-loaded and the usage instruction follows immediately; every clause (limits, rules, rationales) earns its place by telling the agent what the response holds.

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 describe the return content, and it does so concretely (numeric limits with examples, behaviour rules, and per-rule rationale). It omits any indication of response shape or whether limits are global or per-account, which is the only shortfall for a no-parameter 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?

The input schema defines zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies: no parameter semantics are needed and none are missing.

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 names a concrete resource (the published LinkedIn safety limits LinkFetch enforces) and enumerates what it contains: numeric limits, behaviour rules (working hours, spacing, warm-up), and their rationales. An agent knows exactly what comes back. It does not, however, differentiate itself from the closely named siblings linkfetch_safety_status and linkfetch_safety_resume, which is the one gap.

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 gives a clear triggering condition: 'Use it to explain a safety_limit error to the user.' That is a real usage context, not an implied one. It stops short of naming the alternative tools (safety_status, safety_resume) or stating when not to use it, so it lands below the explicit when/when-not bar.

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