Execute MCP Tool

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

Annotations provide limited safety information (readOnlyHint=false, destructiveHint=false, openWorldHint=true), but the description adds no behavioral context such as potential side effects, required permissions, or error behavior. It does not contradict annotations but also fails to enrich them with useful operational details.

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 a single, compact sentence that conveys the core purpose without redundancy. It is appropriately sized and front-loaded with the action verb.

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 dynamic tool that can invoke arbitrary MCP tools, the description lacks critical context: how to obtain valid server_id/tool_name combinations, what arguments should look like, and what side effects may occur. There is no output schema, so the description must compensate but does not.

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 schema already describes all three parameters (server_id, tool_name, arguments). The description adds no extra parameter semantics, such as how to structure the arguments object for the target tool, but the baseline of 3 is appropriate given full schema coverage.

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 action (invoke) and the resource (a tool exposed by a registered MCP server), using a specific verb+resource structure. This distinguishes it from sibling tools like listing or managing MCP servers, making the purpose 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?

No guidance is provided on when to use this tool versus alternatives, nor are prerequisites mentioned (e.g., needing a registered server or discovering available tools via lyzr_list_mcp_server_tools). The description is silent on context and exclusions.

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