Get workflow skill

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

The annotations already establish that this is a safe, read-only, non-destructive, non-open-world operation, so the description does not need to repeat that safety profile. It adds that the tool loads SKILL.md text for the caller to follow, but it does not describe failure behavior for an unknown name or any naming constraints beyond the examples.

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 two sentences with the core action and naming convention front-loaded, followed by a clear usage condition. There is no redundant or filler wording.

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 simple one-parameter, read-only tool with an output schema, the description covers the essential purpose, naming examples, usage condition, and follow-up action. The main missing context is how an agent should discover valid skill names, especially since list_skills is a sibling tool.

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 carry parameter meaning, and it does: the single required name should look like houdini-camera or houdini-solaris and refers to a houdini-* SKILL.md. It still leaves some details implicit, such as exact case sensitivity or whether the .md extension is ever accepted.

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 uses a specific verb ('Load') and resource ('houdini-* SKILL.md') and supplies concrete examples such as houdini-camera and houdini-solaris. It clearly distinguishes loading a skill from listing or searching, but it does not explicitly name the sibling list_skills as the discovery mechanism.

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?

It says to call the tool when the user task matches a skill's topic and adds useful context about non-houdini_mcp workspaces, then instructs the agent to follow the loaded skill text. It gives clear usage context but does not state when not to use it or explicitly point to list_skills for finding valid names.

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