Compose a post-job transaction (unsigned)

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

Beyond annotations (readOnlyHint: false, destructiveHint: false, idempotentHint: true), the description discloses concrete behavioral details: the output is unsigned base64 msgpack, no key is used/held, nothing is submitted, and the spec is committed by hash to prevent changes. This adds significant context beyond the annotations alone and contains no contradiction.

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 long, front-loads the primary action and output, and every sentence adds meaningful detail (output format, signing authority, immutability). There is no redundancy or filler.

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 transaction composer with no output schema and no nested objects, the description adequately covers what the tool returns (unsigned base64 msgpack plus plain-language summary), the safety model (no submission/key), and the commitment property of specHash. It is complete for this level of complexity.

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?

The input schema provides 100% parameter descriptions, so the baseline is 3. The description adds a contextual note that 'the spec is committed by hash' which reinforces the role of specHash, but does not add new format or syntax details for the parameters. Thus it does not exceed the schema's coverage.

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 opens with 'Compose a ValidationRegistry post_job call and return it UNSIGNED as base64 msgpack', naming a specific verb (compose), resource (ValidationRegistry post_job), and distinguishing output format. This clearly differentiates it from sibling tools like ripar_search_agents or ripar_get_agent, which are read-only queries.

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 description states that 'Nothing is submitted and no key is used or held: a human or wallet signs and broadcasts,' which tells the agent when to use this tool (to prepare an unsigned transaction) and what it will not do (submit). It does not explicitly name alternative tools, but the sibling list contains no other transaction composer, so the context is clear.

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