cf_purge_cache

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds the crucial gating requirement (SEO_MCP_ALLOW_DESTRUCTIVE) which is important behavioral context. No contradiction with 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 consists of two concise sentences: the first states the purpose and the second notes the gating requirement. No extraneous text; every word adds value.

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 annotations and lack of output schema, the description covers the core purpose and access control. It does not detail success/error responses or rate limits, but for a simple cache purge tool, the completeness is adequate.

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 descriptive parameter descriptions. The tool description does not add any additional semantic information about the parameters beyond what the schema already provides, so baseline 3 is appropriate.

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 the specific verb 'Purge' with the resource 'Cloudflare cache' and explains the purpose ('so crawlers refetch updated content'). It clearly distinguishes from the sibling tool 'cf_purge_cache_all' which purges all cache, making the scope explicit.

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 indicates when to use the tool ('gated: requires SEO_MCP_ALLOW_DESTRUCTIVE=true') and implies it is for specific URL purging after content updates. However, it does not explicitly state when not to use it or compare with 'cf_purge_cache_all', though the sibling name provides context.

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