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

Annotations already cover readOnly/idempotent/non-destructive, yet the description still adds real behavior: a named permission ('See your taste profile') granted separately from menu access, and the caveat that entries are the user's own statements rather than medical facts, with an instruction to confirm allergens. That is material context an agent could not infer from structured fields.

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?

Front-loaded with the usage trigger, and each clause carries distinct information (triggers, contents, read-only, safety caveat, permission). It is one dense paragraph rather than separated lines, which makes the permission constraint slightly harder to scan than it could be.

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?

Though an output schema exists and return values need not be spelled out, the description still summarizes the payload, and it covers auth requirements, the medical-fact caveat, and the failure fallback. Nothing an agent needs to call this correctly is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and no schema semantics are missing. Baseline 4 is appropriate.

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 and resource ('Returns the user's saved taste profile') and enumerates exactly what that profile contains: likes, dislikes, allergies, diets, five taste levels, food personality, and recently picked/turned-down dishes. The 'Read-only' line makes it clearly distinct from the sibling update_taste_profile.

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?

Gives two explicit triggers ('when the user asks what ChefBear knows about their food tastes' and 'when choosing dishes for them') plus a when-not/fallback path: if the permission is missing, ask the user directly instead. This routes the agent without guesswork.

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