source_cache_get

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

Description indicates read-only operation, but no annotations are provided. Does not disclose behavior on cache miss, error handling, or any side effects. Minimal for a simple read tool.

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, no redundant information. Efficiently communicates core functionality.

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?

Given simple tool with one parameter and no output schema, description is adequate but lacks details on return values or behavior when entry not found. Could be more 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?

Schema coverage for url parameter is 0%. The description does not explain the parameter beyond its name, but 'url' is self-explanatory. No format or constraints provided.

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 'Read persistent source cache entry for a URL', specifying verb (Read) and resource (cache entry for a URL). Distinguishes from sibling source_cache_put (write).

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?

No explicit when-to-use or when-not-to-use guidance. While the description implies reading cached data for a URL, it does not mention alternatives or conditions like cache misses.

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