preflight_url

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: no network fetch occurs, DNS/redirects are unchecked for domain names, and a manual_review verdict is not a safety guarantee. That final warning about result semantics is genuinely valuable. It stops short of describing the full result taxonomy or any rate/limit behavior.

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?

Three short sentences, front-loaded with the core action, and each sentence adds a distinct constraint (no fetch, unchecked aspects, result caveat). No filler, though the trailing caveats could be tightened into one line.

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 tool with no annotations and no output schema, the description covers the essential limitations an agent needs before trusting the result. The main residual gap is that it only names one result value (manual_review) and does not outline the other outcomes, which matters more given there is no output schema.

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 0% and the single 'url' parameter is undocumented in the schema. The description contextualizes what the URL is evaluated against (syntax, literal IP red flags) but adds no format, encoding, or validation guidance for the parameter itself. The parameter name is largely self-explanatory, keeping this at a 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 verb and scope: 'Evaluate syntax and literal IP red flags without fetching a URL.' This clearly defines both the action and its static, non-network nature. It is distinguishable from siblings like audit_openapi, though it does not explicitly name them.

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?

The phrase 'without fetching a URL' implies when this is appropriate (a cheap pre-check) and the DNS/redirect caveat implicitly tells the agent when the result is insufficient. However, it never names an alternative tool or states explicitly when to prefer this over a full fetch/audit, so usage is only implied rather than directed.

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