create_hda

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation (creating/defining an HDA file) but says nothing about whether the destination file is overwritten, what happens to the source subnet node, required permissions, or error behavior. For a write operation with zero annotation coverage, this is a significant 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 and efficient, but the Args block is boilerplate that largely duplicates the schema and even includes 'ctx: MCP context,' which is not a tool parameter. This noise dilutes an otherwise reasonably sized 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?

With no annotations, no output schema, and 5 parameters at 0% schema coverage, the description should do much more. It does not explain the result of the operation, what the created HDA contains, or how the source subnet is handled, leaving the agent under-informed for a mutating call.

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, and it does so only thinly. It adds marginal meaning ('Subnet node path' clarifies the node must be a subnet; 'destination HDA file path' clarifies directionality; 'Operator type name'), but most entries just restate the parameter names with little additional syntax or constraint detail.

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 opens with a specific verb+resource: 'Create a new HDA from an existing subnet node,' which clearly conveys both the action and the source. It does not, however, differentiate itself from close siblings like install_hda, update_hda, or reload_hda, leaving the agent to infer the distinction.

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?

There is no guidance on when to use this tool versus the many HDA-related siblings (install_hda, update_hda, get_hda_info, etc.). The usage is only implied by the verb 'Create,' and no prerequisites or conditions are stated.

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