Make portable tox

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the write nature is known. The description adds no behavioral specifics beyond 'save' and 'write' — no mention of overwrite behavior, permissions needed, or side effects on the source COMP. With annotations present, the description adds minimal value.

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 sentence of 13 words — concise but at the expense of completeness. It lacks structure such as bullet points or sections. While not verbose, it is too minimal to be optimally helpful.

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 moderate complexity (4 parameters, 0% schema coverage, no output schema, destructive hint), the description is severely incomplete. It does not explain what a .tox package is, what a tdmcp-component manifest contains, or any constraints on parameters. The tool needs significantly more context.

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%, yet the description does not explain any parameters. comp_path and out_dir are required but not described. name and docs are optional but lack any explanation. The description fails to add meaning beyond the bare schema 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 specifies the verb 'Save', the resource 'COMP' (component node), the output format '.tox package', and the additional action of writing a manifest. This clearly defines what the tool does and distinguishes it from siblings like 'save_component_to_vault' or 'export_network_to_vault'.

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 versus alternatives. It does not mention exclusions, prerequisites, or typical scenarios. For example, it could indicate that this is for creating portable packages for distribution, whereas other tools are for saving to vault.

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