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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose whether this is a read-only operation, whether it requires authorization, how drift evidence is computed, pagination behavior, or any side effects. It only says what data is returned, leaving the operational profile largely opaque.

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 front-loaded sentence with no filler. It is appropriately concise, though its brevity contributes to under-specification elsewhere rather than being a structural flaw.

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?

The tool has five parameters, no schema descriptions, no annotations, and no description-level parameter or usage guidance. Although an output schema exists and need not be explained in the description, the description is still not complete enough for an agent to invoke this tool correctly in a field of many similar MCP-related recipes.

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 schema has five parameters (decision, namespace, tool_name, surface_id, source_kind) with 0% description coverage. The description mentions none of them, so it adds no semantic guidance about what any parameter controls or how to combine them.

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: it returns pinned MCP tool descriptions, schemas, annotations, and drift evidence. That is clearer than a tautology and tells an agent the tool is about MCP tool-surface drift. However, it does not distinguish this tool from nearby siblings such as recipes_mcp_tool_risk_contract or recipes_mcp_upstream_tools, so it falls short of a 5.

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 states only what is returned, not when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or sibling routing among the many recipes_* tools. An agent gets no clear usage guidance.

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