swap_meal

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

No annotations exist, so the description carries the full burden. It discloses that the tool 'clears any leftover marking on that day', indicating a side effect beyond a simple swap. However, it does not mention authentication, rate limits, or whether previous recipes are replaced permanently.

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 two sentences with zero wasted words. The core purpose is front-loaded, and the usage guideline is appended efficiently. Every sentence earns its place.

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 two-parameter mutation tool with no output schema or annotations, the description provides adequate context: purpose, side effect, and usage flow. It mentions clearing markings and references a sibling tool. Minor gap: no explanation of 'leftover marking' or return value, but overall sufficient.

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?

With 0% schema description coverage, the description must compensate. The example implies date is a day (e.g., 'Tuesday') and recipe_id selects a specific recipe, adding meaning beyond bare schema titles. However, it does not specify expected formats (e.g., ISO date) or that recipe_id might require prior existence.

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 tool replaces a meal on a specific day with a specific recipe, using a concrete example ('put tacos on Tuesday instead'). It distinguishes from siblings like suggest_recipes by explicitly calling it a 'literal per-day override' and contrasting it with the recommendation flow.

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 explicit guidance: use it to replace a day with a specific recipe, and if the goal is to make a day quicker, call suggest_recipes first. This clear when-to and when-not advice helps the agent decide correctly.

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