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

With no annotations, the description carries the full burden, but 'List' strongly implies a non-destructive read and 'optional ... configured' conveys that results may be empty. It still does not state read-only status explicitly, permissions, or anything about result size/pagination, so it adds only mild behavioral context.

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; every word contributes to identifying the resource and its scope.

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 trivial 0-param list tool with an output schema, the description is adequate, but in a crowded sibling set (upstream_call, upstream_context, upstream_tools, servers_list) it fails to give the agent enough to route confidently. It is minimally viable but leaves a clear routing 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool is 4.

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 (List) and resource (optional upstream MCP servers configured for this Security Recipes server), which is clearer than most siblings. However, it does not differentiate itself from closely-named siblings like recipes_mcp_servers_list, recipes_mcp_upstream_tools, or recipes_mcp_upstream_context, leaving the agent to infer the boundary.

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 offers no when-to-use context, no prerequisites, and never names an alternative among the several upstream-related siblings. The agent must guess whether this or recipes_mcp_upstream_tools/context is the right call.

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