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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says the tool 'returns' mappings. It does not mention read-only behavior, filtering effects, data source, authentication, or any operational characteristics beyond the bare action.

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 short sentence that front-loads the action and resource. It is appropriately concise, though it sacrifices useful detail in favor of brevity.

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 tool with five optional parameters, no annotations, and no schema-level descriptions, the description is too thin to let an agent reliably know how to filter or interpret the mappings. The output schema exists, but the operational context and parameter semantics are missing.

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%, and the description adds no parameter information. The five parameter names (status, source_id, control_id, standard_id, capability_id) are somewhat self-explanatory as filters, but the description does not explain how they combine or constrain the returned mappings.

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?

Description names a specific action ('Return') and resource ('standards-to-evidence mappings'), scoped to agentic AI, MCP, and prompt-injection guidance. It is not a tautology and conveys what the tool produces, though it does not explicitly contrast with any sibling tools.

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?

No guidance is given about when to use this tool rather than one of the many similar 'recipes_*' siblings. The intended use is only implied by the resource phrase; there are no conditions, exclusions, or alternative tool references.

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