export_rebuild_bundle

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

No annotations are present, so the description must fully disclose behavior. It mentions output location but omits side effects (e.g., overwriting, deletion, or resource consumption). The tool bundles multiple elements, but the description does not state if any existing data is modified or destroyed.

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?

One sentence, no wasted words. It efficiently conveys the core action and output destination. Ideal length.

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 lack of annotations, output schema, and 0% schema coverage, the description is insufficient. It does not explain return values, preconditions, or what happens to previously stored artifacts. The tool has four parameters, but only three are implicitly referenced. Crucial context is 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?

Schema description coverage is 0%, so the description must compensate. It hints at the purpose of includeNetwork and includeHooks by listing network samples and hooks, but it does not explain envProbes (an array of objects) or how the boolean flags affect behavior. The mapping is weak.

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 verb 'Bundle' and lists the resources being bundled (cached scripts, hook samples, etc.), with a specific output path. This makes the tool's primary function clear, but it does not differentiate from sibling tools like 'collect_code' or 'export_session_report'.

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 (e.g., collect_code, export_session_report). The description does not mention prerequisites, typical use cases, or scenarios where this tool is preferred.

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