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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no behavioral details beyond stating randomness, which is already implied by the name. It does not contradict annotations, but also provides no extra transparency (e.g., whether results can repeat, how many results are returned).

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 brief and front-loaded with the main function. The trigger list adds some redundancy but is useful for an agent to recognize user intent. It is not overly verbose.

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 simple read-only tool with good annotations and 100% schema coverage, the description adequately conveys purpose. It does not explain the return format, but 'a random recipe' implies a single result. This is sufficient for the tool's low complexity.

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 covers 100% of parameters with descriptions for cuisine and mealType. The description only repeats 'Optionally filter by cuisine or meal type' without adding new meaning, so it meets the baseline for schema-covered parameters.

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 clearly states the verb and resource: 'Get a random recipe suggestion.' It also mentions optional filters, which distinguishes it from sibling tools like recipes_search or recipes_get that are not random. The purpose is immediately obvious.

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 provides clear context for when to use it ('when you can't decide what to cook') and includes trigger phrases like 'surprise me' and 'random recipe.' However, it does not explicitly contrast with alternatives such as recipes_search or recipes_get, which would earn a 5.

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