Dietary Export Scientific Follow Up Queue Bundle

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds only 'machine-readable' and 'readiness-side' context; it does not describe output details, prerequisites, or side effects, but it does not contradict 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?

Single sentence, front-loaded with the action, and free of filler or redundant content.

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 conveys the core function but omits workflow context: it does not mention that a dossier and readiness assessment must be supplied, nor how this queue-bundle export differs from the related scientific-follow-up exports. An output schema exists, which reduces the need to document return values, but the missing usage context is still a clear gap.

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 sole 'request' parameter is a complex object requiring a dossier and assessment, but the description provides no parameter-level guidance and the schema has no field descriptions. With 0% schema description coverage, the agent must infer the payload structure entirely from type names and required fields.

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 a specific verb ('Export') and identifies a distinct resource ('machine-readable queue handoff for readiness-side scientific follow-up items'). This clearly separates it from sibling tools like review-board or owner-handoff exports.

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 phrase 'readiness-side scientific follow-up items' implies when the tool is relevant, but there is no explicit when-to-use guidance, no exclusions, and no comparison to the many sibling scientific-follow-up export tools.

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