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

No annotations are provided, so the description must carry the behavioral burden. It does convey that this is a read/enumeration operation surfacing 'local allow decisions', which is useful policy context beyond a plain list. It stops short of stating read-only guarantees, auth requirements, or result shape.

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 core action and the extra 'allow decisions' output are stated efficiently. It is appropriately sized, though it packs two behaviors into one clause without elaboration.

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 with no annotations and an undocumented required server_id, the definition leaves the agent guessing on identifier semantics and on how this differs from the adjacent upstream_context/upstream_call tools.

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?

There is one required parameter (server_id) with 0% schema description coverage, and the description says nothing about what server_id is, where it comes from, or its expected format. The schema documents only its type, so the meaning of the identifier is left entirely to inference.

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 states a specific verb and resource: 'List tools exposed by a configured upstream MCP server', plus the extra behavior of showing local allow decisions. It is clearly distinguishable from recipes_mcp_upstream_call (which would invoke a tool), though it does not explicitly contrast with recipes_mcp_upstream_context or recipes_mcp_upstream_servers.

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?

Usage is implied by the phrasing ('list tools exposed by a configured upstream MCP server'), so an agent can infer this is the enumeration step for a given server_id. However, no explicit when-to-use, prerequisites, or named alternatives (e.g., upstream_context, upstream_call) are provided.

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