cacheserve

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

Describes caching behavior (returns cached if recent, fetches otherwise) and includes cost, but no annotations are provided to supplement behavioral traits like auth or error 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?

Extremely concise single sentence that conveys purpose, behavior, and usage context without any waste.

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 simple caching fetch tool with no output schema and few parameters, the description covers core behavior. Could mention limitations like max URL length or supported protocols.

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 has two parameters with 0% description coverage. Description only implies url and caching (ttl_seconds is hinted but not explicitly connected to the parameter). Minimal added value.

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 fetches a URL with caching, and distinguishes from siblings which are unrelated tools like list_services and docconvert_text.

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?

Explicitly advises 'Use before any fetch that might be repeated', providing clear context for use, though no exclusion criteria are given.

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