http_add_caching

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Add response caching layer' and 'Pro feature', but does not mention side effects, whether it modifies files, whether API key authentication is required, reversibility, or what output to expect. This is insufficient for a mutating tool with no annotations.

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 a single concise sentence with no filler, and 'Pro feature' is a useful caveat. It is front-loaded and readable, though its terseness contributes to missing guidance rather than being a structural flaw.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not explain prerequisites, what files or code will be changed, how to verify the result, or what 'Pro feature' means operationally. An agent would likely need additional information to call this tool confidently.

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 description coverage is only 50%: 'directory' is documented but 'api_key' is not. The description adds no meaning to either parameter and does not explain how 'Pro feature' relates to the api_key field, leaving a key part of the input schema unexplained.

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 states a specific action ('Add response caching layer') and the tool name 'http_add_caching' clarifies the HTTP context, distinguishing it from sibling caching tools like gha_add_caching, proxy_add_caching, and qbatch_add_caching. It is clear about what the tool does, though it does not explicitly mention HTTP in the description.

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 guidance is given about when to use this tool versus alternatives such as gha_add_caching or proxy_add_caching. The only contextual note is 'Pro feature', which hints at access restrictions but does not explain selection criteria or when not to use it.

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