rh_search_workflows

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: constraints are never weakened, so a failed match yields no relaxed results rather than a fuzzy fallback. However, it says nothing about permissions, ranking, pagination, or whether an empty result is the failure mode — significant gaps for a 4-param search tool with zero annotation coverage.

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 filler; the strict-matching behavior is appended efficiently after a semicolon. It is tight, though the compression leaves the parameter and result semantics unaddressed.

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 tool with four undocumented parameters, a nested free-form object, no output schema, and no annotations, this one-line description is too thin — an agent cannot tell what a hard_constraints key looks like, what required_roles must contain, or what a no-match response returns.

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 barely does: 'hard scene requirements' loosely gestures at hard_constraints and required_roles. output_kind (image/video/audio) and backend_profile_id are never explained, and no format examples are given for the nested object.

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 (Search) and resource (registered workflow library), which cleanly separates it from the model-oriented sibling rh_search_models. It does not explicitly name a sibling to contrast against, but the resource is unambiguous.

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?

The phrase 'using hard scene requirements' implies the tool is for constraint-driven lookup, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as rh_get_workflow (fetch one by id) or rh_search_models. Usage must be inferred.

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