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

With no annotations, the description carries the full disclosure burden. It usefully reveals that the returned record is 'publicly documented' and carries 'official setup and safety guidance', which scopes the content, but says nothing about what happens when server_id is unknown or whether the call is cached/read-only.

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 the resource and payload described up front and zero filler.

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 no explanation, and the description at least characterizes the payload. However, for a required lookup key at 0% schema coverage, the absence of any server_id semantics leaves an operational gap.

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% for the single required server_id parameter, so the description must compensate and does not. It never states whether server_id is a slug, UUID, or name, or any format/validity constraint.

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 gives a specific verb and resource: return one documented MCP server, along with its setup and safety guidance. The word 'one' implicitly distinguishes it from the plural list sibling (recipes_mcp_servers_list), though that sibling is never named.

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 only implied by the singular 'one' versus the sibling list tool; there is no explicit statement of when to fetch a single server versus listing or searching. No prerequisites, lookup-key guidance, or error behavior are given.

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