zap.proxy_process

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. It mentions 'enhances with AI intelligence' but doesn't explain what this means in practice—e.g., whether it modifies requests/responses, adds headers, handles errors, or has rate limits. For a tool with no annotations and potential side effects, this is a significant gap in transparency.

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, efficient sentence that states the core purpose. However, the phrase 'enhances with AI intelligence' is vague and could be more specific to earn its place, slightly reducing clarity. Overall, it's front-loaded and avoids unnecessary verbosity.

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 no annotations, no output schema, and a vague description, the tool's behavior is inadequately explained. The description hints at AI enhancement but doesn't detail what this means for inputs, outputs, or side effects. For a tool with 4 parameters and potential complexity, this leaves significant gaps in understanding how to use it effectively.

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 input schema already documents all parameters (method, url, headers, body) with basic descriptions. The description doesn't add any meaning beyond this, such as explaining how 'AI intelligence' affects parameter usage or providing examples. Baseline 3 is appropriate when the 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 states the tool 'Process a request through the MCP proxy layer' which provides a verb ('process') and resource ('request'), but it's vague about what 'enhances with AI intelligence' means operationally. It doesn't distinguish from sibling tools like 'zap.send_request' which might handle similar HTTP operations, leaving ambiguity about when to use one versus the other.

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 provided on when to use this tool versus alternatives. The description mentions 'enhances with AI intelligence' but doesn't clarify what this enhancement entails or when it's beneficial compared to other HTTP request tools in the sibling list, such as 'zap.send_request'. There's no explicit context or exclusions stated.

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