rh_get_workflow

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

No annotations are provided, so the description carries the full burden. It does disclose two useful traits — the revision is immutable (read-only assumption) and the response includes a validation report — but omits permission requirements, error behavior, and what happens for a missing revision. For a tool with zero annotation coverage this is thin.

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 front-loaded sentence with no waste. It is arguably too terse for the semantic burden it must carry, but there is no padding or redundancy.

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 0% parameter description coverage, the description is the only source of semantics and leaves critical gaps: revision_id optionality/default, error cases, and how this differs from the many sibling workflow tools.

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% for both workflow_id and revision_id, and the description explains neither. It never says that revision_id is optional (the schema marks only workflow_id required) or what the default revision is when omitted, which is the key caller decision here.

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?

States a specific verb+resource ('Read a ... workflow revision') and adds a scoping qualifier ('local immutable') plus the return content ('validation report'). It does not differentiate itself from close siblings like rh_search_workflows or rh_validate_workflow, so it falls short of a 5.

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 call this versus rh_search_workflows (to find a workflow), rh_validate_workflow (to validate one), or rh_export_workflow. The agent must infer usage purely from the tool name.

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