slim_fetch

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

With no annotations provided, the description carries full behavioral disclosure burden. It reveals SLIM's output levels (L1, L3, L5, L7), token reduction benefit, and supported platforms, which adds meaningful context beyond the schema. It does not cover error handling or default behavior, but the provided transparency is substantial.

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 front-loaded with purpose and usage, then uses compact bullet lists for SLIM levels and supported platforms. Each section earns its place, though it is longer than strictly necessary, which keeps it from a 5.

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?

Even without an output schema, the description explains what the response contains (SLIM levels) and which content types are supported. It lacks explicit indication of the default output level and does not compare to the sibling tool, but for a single-parameter tool this is adequately complete.

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 schema describes the single URL parameter fully, including protocol auto-completion, at 100% coverage. The description does not add parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 "Fetch web content in SLIM format" – a specific verb plus resource, clearly stating what the tool does. It does not explicitly differentiate this from the sibling slim_fetch_with_options, so it stops short of a 5.

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 provides clear guidance: "Use this tool when you need to read and understand web pages, articles, documentation, or any online content." However, it does not mention when not to use it or when to prefer slim_fetch_with_options, so it lacks exclusions and alternative comparisons.

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