Clear Cache

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

The description indicates the tool clears cache, a mutation, and returns an operation_id (implying async). However, no annotations for destructiveHint or readOnlyHint exist. The openWorldHint annotation does not provide behavioral clarity. The tool does not disclose potential impacts (e.g., temporary performance degradation) or authorization needs.

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?

Two concise sentences: first states action, second states return value. No unnecessary words or redundancy. Efficient and front-loaded.

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 the existence of similar cache-clearing sibling tools (CDN, edge cache), the description lacks differentiation. It does not explain what 'server cache' entails or how the operation_id is used. An output schema exists but is not detailed in the description. The tool's simplicity partially compensates.

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 is 100% with a single required parameter 'environment_id' and its description. The tool description does not add any additional meaning beyond the schema. Baseline 3 is appropriate as schema already covers the parameter.

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 clears the server cache for an environment and returns an operation_id. The verb 'clear' and resource 'server cache for an environment' are specific. However, given sibling tools like 'kinsta.cdn.clear-cache' and 'kinsta.edge-cache.clear', the description could explicitly distinguish server cache from CDN or edge cache, though 'server' provides some differentiation.

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 on when to use this tool versus alternatives like CDN or edge cache clearing. No prerequisites or when-not-to-use information provided. The description only states what it does, not when it should be invoked.

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