Dietary Lookup Analytical Method Evidence

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds 'governed' and 'supported' to indicate curated data and family restrictions, but these are partially captured by the schema enum. There is no contradiction between description and 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 a single, well-front-loaded sentence that directly states the tool's purpose without any redundant words. It efficiently communicates the core function.

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 tool has a nested request structure with five fields, and while the output schema exists, the description fails to explain the meaning or expected values of the optional parameters. The schema enum helps for contaminantFamily, but analyte, authority, matrixGroup, and jurisdiction remain opaque. The description is too sparse to guide correct invocation for a moderately complex input.

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%, and the description contains zero information about the request object or its fields (contaminantFamily, analyte, authority, matrixGroup, jurisdiction). The optional parameters are entirely undocumented, and the description does not compensate for the lack of schema descriptions.

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 returns 'governed analytical-method-evidence records' for 'supported contaminant monitoring families.' This specific verb-resource combination distinguishes it from sibling lookup tools like dietary_lookup_contaminant_legal_limits or dietary_lookup_occurrence_evidence, though it doesn't explicitly name alternatives.

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 when analytical-method-evidence records are needed for contaminant monitoring families, but it provides no explicit guidance on when to prefer this over sibling lookup tools such as dietary_lookup_method_support or dietary_lookup_occurrence_evidence, nor does it mention any exclusions or prerequisites.

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