pdf_cache_clear

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

With no annotations, the description carries full burden for behavioral disclosure, but it fails to mention side effects (e.g., whether clearing cache is destructive, if it impacts ongoing operations, or any permission requirements). The single sentence 'Clear the PDF cache' provides no insight into behavior beyond the action itself.

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 extremely concise at four words, which is efficient but arguably too brief. It front-loads the action but omits necessary context. While there is no redundancy, the brevity compromises completeness.

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?

Despite having an output schema (not shown), the description does not explain any return values or post-conditions. The tool's context is minimal: it clears a cache, but an agent would benefit from knowing what happens after execution (e.g., success indication, number of cleared entries).

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 provides 100% coverage for the single parameter 'expired_only', including its type, default, and description. The description adds no additional meaning beyond what the schema already conveys, so the baseline of 3 applies.

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 uses a clear verb ('Clear') and resource ('PDF cache'), effectively conveying the tool's primary function. However, it lacks specificity about what 'clear' entails (e.g., removing all cached files or just marking for invalidation). It distinguishes from siblings like pdf_cache_stats, which likely provides statistics rather than mutation.

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 usage guidance is provided. The description does not indicate when to use this tool (e.g., before reading fresh PDFs) or when not to use it (e.g., if cache is needed for performance). No alternatives or prerequisites are mentioned.

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