Fastly NGWAF MCP Server

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. 'Manage' implies both read and write operations, but the description doesn't specify permissions required, whether operations are destructive, rate limits, or what happens on success/failure. It mentions no behavioral traits beyond the vague 'manage' concept, leaving critical operational context undefined.

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 at just two words, with no wasted language. However, this brevity comes at the cost of being under-specified - it's too short to be genuinely helpful. The structure is front-loaded but lacks substance, making it efficient but incomplete rather than optimally concise.

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 tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the multi-action nature (list/get/update/invite/delete), doesn't clarify what 'manage' entails operationally, and provides no context about return values or error conditions. The description fails to compensate for the lack of structured metadata.

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 5 parameters with descriptions and enums. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain parameter relationships, dependencies, or provide usage examples. The baseline of 3 is appropriate since the schema does the heavy lifting, but the description doesn't enhance understanding.

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 corporation users' is a tautology that essentially restates the tool name 'manage_users' with the addition of 'corporation'. It doesn't specify what management actions are possible (list, get, update, invite, delete) or what resources are affected. While it mentions 'corporation users', it doesn't distinguish this from sibling tools like 'manage_alerts' or 'manage_blacklist' in terms of resource type.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions. For example, it doesn't clarify whether this is for bulk operations versus individual user management, or how it differs from other user-related tools that might exist in the system (though none are listed among siblings).

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