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

With no annotations provided, the description carries the transparency burden. It does disclose a key behavioral trait: the tool only calls 'allowed read-only' tools, which implies safety and authorization constraints. But it does not explain argument forwarding, error behavior, or network/server-side effects beyond that.

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, well-structured sentence with no filler. It front-loads the core action and constraints in an efficient, readable way.

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 generic proxy-invocation tool, the description is too thin. It does not explain how to discover valid server_id or allowed tool_name values, what arguments should contain, or how the output schema relates to the upstream tool. The output schema exists, but the invocation context remains under-specified.

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 0%, so the description must compensate. It clarifies that server_id refers to an upstream MCP server and tool_name to a tool on it, but it never explains the 'arguments' parameter—how it is passed, whether it is required, or what shape it should take. This is a meaningful gap.

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 uses a specific verb and resource: 'Call an allowed read-only tool on a configured upstream MCP server.' It clearly distinguishes itself from related siblings like recipes_mcp_upstream_tools or recipes_mcp_upstream_servers, which list or inspect rather than invoke a tool.

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?

The description implies use when you need to invoke a read-only tool on an upstream MCP server, and the 'allowed' wording signals a restriction. However, it does not explicitly say when not to use it or point to sibling tools for discovering available servers or tools.

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