rh_import_workflow

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

With no annotations, the description carries the full burden, but it does disclose one genuinely useful behavioral fact: 'no provider task is submitted,' which distinguishes it from execution tools like rh_run_workflow. It still omits whether import mutates project state, idempotency, overwrite behavior, and permission requirements.

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?

A single tightly-packed sentence with the key constraint ('no provider task is submitted') front-loaded and no filler. It is efficient, though the compressed dual-mode phrasing slightly hurts readability.

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 4-parameter tool with no annotations and no output schema, the description is thin. It leaves unclear what the tool returns (discovered paths? an import result?), what the optional parameters do, and how the two modes differ operationally.

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 coverage is 0% for 4 parameters, so the description must compensate and largely does not. It gestures at a 'registered project' (project_id) and 'import one explicitly' (workflow_id), but says nothing about output_nodes or relative_path, leaving two parameters fully unexplained.

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 names a resource (API-format workflow JSON files) and two actions (discover or import), which is more than a tautology. However, the dual 'discover OR import' framing in a tool named 'import' is ambiguous about the primary purpose, and it does not distinguish itself from close siblings like rh_export_workflow, rh_create_workflow, or rh_get_workflow.

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 when-to-use or when-not-to-use guidance is given, and no alternative sibling is named. An agent cannot tell from this text whether to reach for this versus rh_export_workflow or rh_create_workflow, both of which are adjacent in the workflow lifecycle.

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