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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Return' signals a read-only operation and the payload contents are listed, but the description does not explain drift semantics, filtering behavior, or what 'pinned' means, leaving important behavior unstated.

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 a clear verb and object and no filler or repetition. It is appropriately compact for what it conveys.

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 output schema presumably covers return values, so that is not a missing piece. However, with five undocumented optional parameters and no usage guidance, the description alone is insufficient for an agent to know which arguments to pass or when this tool is appropriate relative to sibling 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?

The schema has five optional parameters and 0% description coverage. The description does not mention decision, namespace, tool_name, surface_id, or source_kind, nor does it explain how these parameters shape the returned result, so it provides no parameter guidance beyond the bare parameter names.

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 uses the verb 'Return' and names a specific resource: 'pinned MCP tool descriptions, schemas, annotations, and drift evidence.' This makes the core function clear and distinguishes it from most sibling recipe tools by focusing on tool-surface drift data, though 'pinned' and 'drift evidence' could be more explicit.

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 gives no when-to-use, when-not-to-use, or alternative-tool guidance. It only states what the tool returns, so an agent must infer when to choose it among the many similar recipes_* packs.

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