Get Food (FatSecret)

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

Annotations already cover safety (read-only, idempotent, non-destructive), so the description's role is lighter. The description adds context about the return content (nutrition detail + servings) but doesn't disclose additional behavior like error cases or auth requirements, which is acceptable given the annotations.

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 one compact sentence with no filler. It front-loads the key outcome (full nutrition detail + servings) and the source context in a readable way.

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 single-parameter read tool with no output schema, the description covers purpose, source, and output scope. It doesn't need to discuss return formatting or errors since annotations and schema handle safety and required parameter.

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 only declares foodId as a string; the description fills in the semantic gap by identifying it as an ID from fatsecret_search_foods, which is critical for avoiding confusion with other ID-based tools. This adds meaningful meaning beyond the schema.

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 retrieves full nutrition detail and servings for a specific food ID. The phrase 'from fatsecret_search_foods' differentiates it from search and entry tools, making the purpose explicit and tied to a clear input source.

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 implies usage after fatsecret_search_foods to obtain the food ID. It doesn't explicitly list when not to use it or alternative tools, but the source hint provides sufficient context for selecting it over sibling tools like get_food_entries or get_recipe.

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