gateway.invoke

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

No annotations provided; description only mentions argument validation and output truncation. Missing disclosure of side effects, authentication needs, or error behavior, leaving significant gaps.

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?

Two concise sentences with no fluff. Every sentence adds relevant information about the tool's core action and behavior.

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?

No output schema; description only mentions truncation. Missing return format, error handling, and prerequisite (server connection). Adequate but not thorough.

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 67%; descriptions for tool_id, arguments, and options are already in schema. Description adds 'output truncated' but that relates to max_output_chars already documented. Minimal extra value.

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?

Description clearly states 'Invoke a tool on a downstream MCP server' with a specific verb and resource, distinguishing it from siblings like 'gateway.cancel' or 'gateway.describe'.

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 explicit guidance on when to use this tool versus alternatives (e.g., gateway.describe for exploring tool schemas). Context is implied but not stated.

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