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

Annotations already declare non-destructive, idempotent and closed-world, yet the description still adds real value: it scopes the blast radius ('dinners, servings and This Week are unchanged') and states an auth prerequisite ('Requires a linked Chop It account') that annotations do not cover. The idempotency sentence partly repeats idempotentHint but clarifies the keying dimension.

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?

Four short sentences, front-loaded with the action and the identifier, then effects, then the prerequisite. Slight redundancy in restating idempotency already declared in annotations, but nothing is wasted.

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?

Output schema exists, so return values need not be explained, and annotations cover the safety profile. The auth prerequisite and non-effects are disclosed, leaving only minor gaps around the title parameter and error cases.

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%, so the description must carry parameter meaning. It names savedWeekId explicitly, but title is only implied by 'Renames' — it never says title is the new display name or mentions the 2–50 character constraint. Half the parameters get real semantics.

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 a specific verb (renames), a specific resource (one of the user's Saved Weeks), and the keying identifier (savedWeekId). This cleanly separates it from delete_saved_week, open_saved_week, list_saved_weeks and save_week without needing to name them.

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?

Usage is implied by 'one of the user's Saved Weeks' plus the account prerequisite, but there is no explicit when-to-use vs. alternative guidance (e.g. when to rename versus save_week creating a new week). An agent must infer the boundary from the sibling names.

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