Dietary Apply Residue Evidence

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is known. The description adds no additional behavioral context, such as whether the input profile is modified or a new merged profile is returned. It does not contradict the annotations, but it also does not enrich them.

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 concise sentence that immediately front-loads the core action ('Merge additional residue evidence'). Every word is relevant, with no filler or repetition.

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 complex tool with nested schemas, an output schema, and domain-specific semantics, a one-sentence description is insufficient. It does not explain how conflicts are handled, whether existing records are replaced, how provenance is managed, or what the tool returns. The description feels incomplete for the complexity of the operation.

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 does not explain the 'request' parameter's structure or key fields like override_existing. While the schema itself is rich, the description adds no meaning beyond the schema and fails to compensate for the low coverage, leaving the crucial merge/override behavior undocumented.

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 'Merge' with clear resources: 'additional residue evidence' and 'existing dietary residue profile'. It distinguishes the tool from siblings like dietary_build_residue_profile (which creates a new profile) and dietary_reconcile_residue_evidence (which reconciles evidence). The action is immediately understandable.

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 provides no guidance on when to use this tool instead of alternatives. It does not mention that it is for extending an already-built profile, nor does it contrast with sibling tools such as dietary_build_residue_profile or dietary_reconcile_residue_evidence. No exclusions or prerequisites are stated.

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