nutrition.food

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

The description mentions key behavioral traits (real analyzed values, includes ingredients for branded foods), but lacks details on error behavior, rate limits, or authentication. Given no annotations, the description carries the full burden and could be more comprehensive.

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 concise (two sentences) and well-structured, with essential information front-loaded. Every sentence adds value without redundancy.

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?

The description covers the main functionality, data sources, and distinguishes two use cases. However, it does not explain pagination parameters or error conditions. Given the absence of an output schema, some additional behavioral context would improve completeness.

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 description adds meaning by explaining the two primary parameters (query and fdcId) with examples, and notes the inclusion of ingredients for branded foods, which relates to the dataType parameter. This goes beyond the schema definitions.

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's function (USDA FoodData Central nutrition lookup) and distinguishes two modes: search by name or fetch by fdcId for full profile. It also highlights real analyzed values vs estimated, providing a clear and unique purpose among siblings.

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 explains when to use each mode (search vs fetch), but does not explicitly state when not to use the tool or mention alternative tools. However, the provided examples offer practical guidance.

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