Fastly NGWAF MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Manage' implies mutation capabilities, but the description doesn't specify permissions required, rate limits, whether changes are reversible, or what the response looks like. It mentions 'whitelist (allowlist)' which adds some context about security/IP filtering, but lacks details on behavioral traits like side effects or error conditions.

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 with a single phrase, 'Manage IP whitelist (allowlist)', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, though this brevity contributes to gaps in other dimensions.

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 tool's complexity (7 parameters, mutation capabilities, no annotations, no output schema), the description is incomplete. It doesn't explain the multi-action nature (list/add/remove), how parameters interact conditionally, what the tool returns, or how it fits into the broader context with sibling tools. For a mutation tool with rich parameters, more guidance is needed.

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 100%, so the schema already documents all 7 parameters with their purposes and constraints (e.g., action enum values, conditional usage for ip/note/entryId). The description adds no parameter-specific information beyond what's in the schema, such as explaining how corpName/siteName defaults work or format details for expires. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Manage IP whitelist (allowlist)' states the resource (IP whitelist/allowlist) and the general action (manage), but it's vague about what 'manage' entails. It doesn't specify the specific operations available (list, add, remove) or differentiate from sibling tools like manage_blacklist, manage_lists, or manage_alerts. The description provides basic purpose but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like manage_blacklist for IP blocking, manage_lists for other list types, or create/delete rules for related operations. There's no context about prerequisites, such as needing corp/site context from set_context or get_context tools. Usage is implied only by the tool name.

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