Get past recipes

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

Annotations already declare this as read-only and non-destructive, lowering the burden. The description adds useful behavioral context by specifying ordering, scope, and the presence of ratings/comments, which goes beyond what the annotations convey.

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 compact: the first sentence packs scope, ordering, and content, while the second gives purpose. Slight phrasing ambiguity in 'for a past week' prevents a perfect score.

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 an output schema, a safe annotation profile, and only one optional parameter with a default, this description is mostly sufficient. The missing limit semantics and lack of explicit sibling routing leave a small but real gap.

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 gives no meaning for the only parameter, 'limit'. It is unclear whether limit caps the number of recipes, weeks, or entries, so the agent is left to guess semantic intent.

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?

States the resource (recipes selected for past weeks), ordering (newest first), and included data (week, status, ratings/comments). This clearly distinguishes it from sibling tools like get_favorite_recipes or get_current_week by targeting historical selections.

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?

Provides explicit use context ('Use to avoid repeats and learn what landed'), which tells an agent when this tool is valuable. However, it does not name alternatives or state when not to use it.

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