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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that only allowlisted read-only upstream tools can be invoked, but says nothing about error/permission behavior, how 'arguments' are forwarded or validated against the upstream schema, or rate/timeout limits.

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 tight sentence with no wasted words, but it is under-specified rather than concise in a useful 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?

An output schema exists so return values need not be explained, but for a proxy-invocation tool with three undocumented parameters and zero annotations, the description omits argument passing, prerequisites, and failure semantics that an agent needs to call it correctly.

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% across three parameters, so the description must compensate and does not. It never explains server_id, tool_name, or the free-form arguments object, leaving the agent to guess how the upstream tool's inputs are passed.

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 ('Call') and resource ('allowed read-only tool on a configured upstream MCP server'), which distinguishes it from sibling listers like recipes_mcp_upstream_tools and recipes_mcp_upstream_servers. It stops short of explicitly naming the alternative it complements, but an agent can infer the proxy/invocation role.

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?

'Allowed read-only' hints at a constraint but there is no when-to-use guidance, no statement of prerequisites (must the server be configured and the tool be allowlisted first?), and no routing against siblings such as recipes_mcp_upstream_tools or recipes_mcp_upstream_context.

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