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

No annotations are provided, so the description carries the full behavioral burden. It states what is returned but omits whether the operation is read-only, what permissions are needed, whether the output is cached or fresh, and any other operational traits.

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 wasted words. It is concise, but its extreme brevity leaves it underspecified for a tool with six unannotated parameters.

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 the description need not explain return values in detail. However, with no annotations, no parameter descriptions, and no usage guidance, the definition is incomplete for helping an agent understand how to invoke this routing pack correctly.

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 6 parameters with 0% description coverage, and the description does not mention or explain any of them. Parameters such as decision, model_id, route_id, risk_tier, provider_id, and workflow_id are left entirely opaque, so the description fails to compensate for the schema gap.

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 a specific verb ('Return') and names the resource types it produces: model-provider route profiles, workflow mappings, and required evidence. It does not, however, differentiate this tool from the many similarly named recipes_* sibling tools, so it falls short of the 5 level.

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 indication of when to use this tool, when not to use it, or which sibling tool is the alternative. An agent has no routing guidance for selecting this pack over the other recipe packs.

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