mesh_invoke_tool

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

No annotations are provided, so the description carries the full behavioral burden. It conveys a direct proxy execution capability but omits critical context such as side effects, permission requirements, error handling, or whether the call is potentially destructive. For a tool that can execute arbitrary downstream tools, this is a major gap.

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 sentences, front-loaded with the core action, and free of redundant or filler content. Every clause contributes to the purpose or parameter mapping.

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 absence of an output schema and annotations, the description should explain what the tool returns or how errors surface. It covers purpose and parameters but leaves return values and failure modes entirely unspecified, which is incomplete for a generic invocation proxy.

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 each parameter is already documented in the schema. The description merely restates the three parameters ('server ID, target tool name, input arguments dictionary') without adding format details or constraints. Baseline 3 is appropriate.

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?

States a specific verb ('execute') and resource ('any tool on a downstream MCP server'), making the action unambiguous. However, it does not explicitly differentiate itself from siblings like mesh_search_tools or mesh_describe_tool, though the execution focus is clear.

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 when-to-use guidance is provided. The description never mentions alternatives (e.g., search or describe first) or conditions that would favor this tool over discovery siblings. Usage is only implied by the verb.

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