workflow_packet

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

The description adds some context beyond annotations by mentioning 'expose watch/surface metadata'. Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. However, the description does not detail what happens to the watch mode or the nature of exposed metadata.

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 single-sentence and front-loaded, but it is too brief for a complex tool with 13 parameters. It sacrifices necessary detail for brevity, making it less useful than a slightly longer, more informative description.

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 tool's high complexity (13 parameters, many enums, nested objects), the description is severely incomplete. It does not explain what a 'typed workflow packet' is, how watch mode works, or how to use the output schema. The description fails to provide enough context for an agent to use the tool correctly.

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 input schema has 0% description coverage, yet the description provides no information about any of the 13 parameters. It fails to explain what parameters like 'family', 'queryKind', or 'scope' mean or how to use them, leaving the agent without essential guidance.

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 identifies the tool's action (generate) and resource (typed workflow packet) and mentions key features (expose watch/surface metadata). However, it does not distinguish from sibling tools like 'context_packet' or 'verification_bundle_artifact', which may have overlapping purposes.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies it is for generating workflow packets from query answers, but does not specify preconditions, exclusions, or when not to use it.

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