Manage TouchDesigner community packages

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

The description adds significant behavioral detail beyond annotations: it explicitly states that the tool never runs third-party scripts, pip installs, model downloads, or external app setup. It also describes the staging process and import conditions. Annotations already indicate destructive and open-world behaviors, and the description reinforces and clarifies them without contradiction.

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 concise, consisting of two sentences. The first sentence front-loads the tool's actions, and the second provides key safety and behavior details. No unnecessary words; every sentence adds value.

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 12 parameters and no output schema, the description covers the overall workflow and safety constraints, but it does not detail the behavior of all actions (e.g., search results, info output). However, the schema descriptions cover individual parameters, so the description provides sufficient high-level completeness.

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?

With 100% schema description coverage, the baseline is 3. The description does not re-document each parameter but adds context for the action parameter by listing actions and explains the dry_run default. This is sufficient, but no extra meaning is added for other parameters beyond the schema's own descriptions.

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 tool manages TouchDesigner community packages with specific actions like search, list, inspect, doctor, dry-run install, stage, and uninstall. It uniquely addresses package management, distinguishing it from the many sibling tools which focus on different tasks.

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 usage context by noting that dry-run is the default and explaining conditions for import (bridge reachable, safe .tox path). Although it does not explicitly contrast with alternatives, the sibling list contains no other package management tools, so usage guidance is adequate.

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