Warm VIPMP docs cache

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

The description adds significant behavioral detail beyond annotations: initial vs. repeated run times, disk cache + ETag revalidation, and returned summary. It is consistent with the idempotentHint and openWorldHint annotations, and no contradictions exist.

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 (3 sentences), front-loaded with the primary purpose, and every sentence provides essential context (purpose, performance, output).

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 zero parameters and that an output schema exists, the description adequately explains the tool's behavior, output ('summary of fetches, cache hits, errors'), and performance characteristics. It is fully complete for its simplicity.

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?

There are zero parameters, so baseline 4 applies. No parameter information is needed, and the description does not attempt to add any.

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 clearly states the tool's purpose: 'Pre-fetch every page in the sitemap' to improve search matching. It distinguishes from siblings like search_vipmp_docs and cache operations by specifying the role in enabling content-level matching.

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 description explains when to use (before searches needing content-level matching) and provides performance context (first run ~30s, subsequent near-instant). However, it lacks explicit guidance on when not to use or alternatives.

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