rh_validate_payload

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

With no annotations, the description must carry the behavioral load. It usefully discloses that the call is side-effect free ('does not execute it'), which is the key trait for a validation tool. It says nothing about what a failed validation produces, whether errors are returned or thrown, or any auth/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 sentence that front-loads the action and appends the important non-execution caveat. No filler; it could carry one more clarifying clause without bloat, but it wastes nothing.

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, a nested free-form payload object, and 0% parameter documentation, an agent still lacks the outcome shape (what a validation result looks like) and the exact meaning of `endpoint`. A validation tool whose whole purpose is producing a verdict should describe that verdict.

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 two required parameters, so the description must compensate. The phrase 'against a public model schema' gives a plausible gloss for the opaque `endpoint` parameter, and 'a payload' names the other, but neither is pinned down (format, whether endpoint is a URL, model id, or schema id).

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 (validate) and a specific resource (a payload) plus the target of validation (a public model schema). It is clear what the tool does, though it does not explicitly distinguish itself from the similarly-named rh_validate_workflow sibling.

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 clause 'this does not execute it' implicitly routes the agent away from rh_run_workflow / rh_prepare_generation for the execution path, which is useful. However, it never states when validation is required, nor does it point to rh_get_model_schema for obtaining the schema or contrast with rh_validate_workflow.

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