Handle MCP gateway protocol requests by public id

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

Annotations indicate not read-only, not destructive, not idempotent. The description adds 'Authorization class: public' which is helpful. However, it does not describe side effects, request handling details, or what happens on success/failure. More context about the MCP protocol would improve 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 very short (two lines plus extra metadata). It is concise but lacks a structured format (e.g., bullet points or sections). The inclusion of operation and authorization class is efficient, but the brevity sacrifices clarity.

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?

The tool has a complex schema with nested objects and an output schema, yet the description provides almost no context. An agent would struggle to use this tool correctly due to missing parameter explanations and lack of behavioral context. The description is too minimal for effective use.

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 0%. Neither the description nor the input schema explains the parameters. The body and gatewayPublicId are not described in the description. The agent gets no guidance on what values to provide, especially for the free-form body object.

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 handles MCP gateway protocol requests by public ID. The verb 'handle' is somewhat generic but the resource and scope are clear from the path and operation. However, it does not differentiate from sibling tools like pc_get_mcp_gateways_by_gateway_public_id or other gateway-related tools.

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. The description does not explain prerequisites, context, or situations where this tool is appropriate. It only provides the operation and authorization class, which is not enough for an agent to decide when to use it.

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