Dietary Export Contaminant Monitoring Interpretation Bundle

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context that the bundle includes governed evidence records and reviewer prompts, but does not explain what 'governed' means or any processing side effects.

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, front-loaded sentence with no filler words, making it concise and immediately readable. It could be slightly more informative, but it earns a high score for efficiency.

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?

Given the complex nested input schema and the large sibling family, the description omits key context: prerequisites (e.g., a prior dietary_check_contaminant_monitoring_import), the meaning of 'interpretation bundle', and how it relates to signoff/dossier exports. The output schema exists, so return values are covered, but operational context is largely 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 description provides no information about the single 'request' parameter, and schema description coverage is 0%. Although the input schema's $defs are rich, the description does not compensate for the lack of parameter guidance, leaving the agent to rely solely on field names.

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 uses the specific verb 'Package' with a clear resource ('a contaminant monitoring check with governed evidence records and reviewer prompts'). It distinguishes the tool from sibling signoff/dossier exports by emphasizing the bundle's composition, though it does not 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 the tool is used to turn a contaminant monitoring check result into an interpretation bundle. However, it provides no explicit when-to-use guidance or exclusions relative to the many sibling tools like signoff packets or review dossiers, leaving selection to inference.

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