mcp_tool_call

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

The description discloses that the tool wraps the call in a JSON-RPC 2.0 envelope and returns the raw response, which is useful. However, it does not state whether the operation is read-only or destructive, or any authentication or rate limit considerations.

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 extremely concise at two sentences and 26 words. It is front-loaded with the core action and provides immediate clarity without unnecessary detail.

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 simple wrapper tool with only two parameters and no output schema, the description provides sufficient context: what it does, the envelope, and the return format. It could mention error handling, but overall it is complete enough.

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 100%, so the parameters are well-described in the schema. The description adds context that the arguments are wrapped into a JSON-RPC call, but this is not essential for understanding parameter meaning.

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 specific action: invoking a tool on the hosted MCP server. It uses a specific verb 'invoke' and identifies the resource (the MCP server at mcp.servonaut.dev). This distinguishes it from sibling tools that have more specialized purposes.

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 generic tool versus the many specialized sibling tools. An agent could benefit from knowing that this tool is for calling MCP tools that are not already exposed as dedicated functions.

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