create_hda

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals only that the tool creates an HDA from a subnet node. It doesn't state whether the source subnet is modified, whether the destination file is overwritten or errors if it exists, whether a cook is triggered, or any side effects. For a creation tool this is a meaningful gap.

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 purpose sentence is front-loaded, followed by a compact structured args list. It is reasonably efficient with no obvious filler. Minor waste: the 'ctx: MCP context.' line references a non-schema parameter, but overall the structure is clean and scannable.

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?

For a creation tool with no output schema and no annotations, the description is incomplete. It doesn't explain the return value, preconditions (e.g., what makes a node a valid 'subnet node'), error behavior if the destination file exists, or side effects on the scene. An agent would have to guess at these details.

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. The args section does add one-line meaning to each parameter ('Subnet node path', 'Destination HDA file path', 'Operator type name', 'Human-readable label', 'Version string') beyond the bare schema titles. However, these are minimal glosses, and the description lists 'ctx' as an arg even though it isn't in the schema, which is slightly confusing. It helps but doesn't fully compensate for the coverage gap.

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 states a specific verb (Create) and resource (HDA) with the source material ('from an existing subnet node'). This distinguishes it from siblings like install_hda, update_hda, reload_hda, and uninstall_hda, which are different lifecycle operations. It's clear but doesn't explicitly name the siblings it differs from.

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 on when to use this tool versus alternatives such as update_hda (for existing HDAs) or install_hda. No exclusions, preconditions, or contextual cues are given. The args listing describes what each parameter is, not when the operation is appropriate.

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