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

No annotations are provided, so the description carries the full disclosure burden. "Inspect" correctly implies a read-only, non-mutating operation, but nothing is said about error behavior when the server or tool_name is invalid, permission requirements, or whether the output is large. Adequate but shallow for a zero-annotation tool.

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?

A single front-loaded sentence with no filler; the purpose and the timing of use are packed into one line with nothing wasted.

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 two-parameter, read-only inspection tool with no output schema, the description covers what it returns (schema and parameter specs) and when to call it. Only minor gaps remain, such as failure behavior for unknown server/tool_name.

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% and both parameters (server, tool_name) are documented in the schema itself. The description adds no format, constraint, or naming guidance beyond what the schema already provides, so it sits at the baseline.

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 gives a specific verb (inspect) and resource (full JSON schema and parameter specifications of a specific tool), which is clearly distinct from sibling verbs like mesh_search_tools and mesh_invoke_tool. It stops short of naming those siblings explicitly, but the action is unambiguous.

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?

"Before invoking it" states a clear condition for use, effectively positioning this as the pre-flight step to mesh_invoke_tool. There is no explicit when-not guidance or named alternative, but the context of use is well established.

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

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.

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

With no annotations, the description carries the full burden, and it does disclose scope and return shape ('across all aggregated MCP servers', 'ultra-compact signatures and relevance scores'). It omits any statement about cost, latency, result ranking behavior, or what happens with an empty/miss result, which an agent would want for a cross-server fan-out search.

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 compact sentences, purpose front-loaded, examples parenthetically embedded without bloat. No filler, though the parenthetical examples are the only slight padding.

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 exists, so the description rightly mentions the return format (signatures + relevance scores), and all three parameters are schema-documented. For a discovery tool with no annotations it is largely sufficient, missing only ranking/pagination behavior and explicit sibling routing.

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 query, limit and server. The keyword examples in the description add modest interpretive value for how to phrase 'query', but nothing beyond that; baseline 3 applies.

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 gives a specific verb ('Search') and resource ('tools across all aggregated MCP servers') plus concrete keyword examples ('git commit', 'read file'). It clearly contrasts implicitly with mesh_invoke_tool/mesh_describe_tool by framing itself as discovery, but never names those siblings to make the distinction explicit.

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?

It says how to search (natural language keywords) but not when to reach for this tool versus mesh_describe_tool, mesh_invoke_tool or mesh_status, and no workflow (search -> describe -> invoke) is suggested. Usage is only faintly implied by the tool's name.

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

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

With no annotations, the description must carry the safety profile; 'inspect' reasonably implies a read-only, side-effect-free call, and 'real-time' is a useful disclosure about freshness. It does not state whether calling it consumes tokens, requires an active connection, or what happens if no servers are connected.

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?

A single front-loaded sentence with a colon-separated list of what is returned; no filler, no restatement of the tool name.

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 zero-parameter, zero-annotation read tool with no output schema, the description covers the essentials of what is returned. It is only slightly short of complete because it omits read-only confirmation and any failure/empty-state behavior.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly presents it as a no-argument call and spends its words on the returned data instead of inventing parameter detail.

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 (inspect) and resource (real-time gateway statistics) and enumerates the three things returned: connected downstream servers, indexed tools, and token savings. That is far more specific than the siblings' search/describe/invoke surface, though it never names or contrasts them explicitly.

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?

There is no guidance on when to call this versus mesh_search_tools or mesh_describe_tool, nor any stated prerequisite (e.g., call before or after connecting servers). Usage is only implied by the word 'inspect'.

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