reinvent_rl_scoring_design_guide

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

With no annotations, the description carries full burden. It discloses that schemas are introspected from the live registry (implying read-only, authoritative data) and explicitly scopes out component definitions, which helps set expectations. However, it doesn't explicitly state read-only behavior or other potential side effects, so a small gap remains.

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 well-structured: a front-loaded purpose sentence, then key notes, steps, and a call-to-action. Every sentence adds value, and the layout (with NOTE and numbered steps) enhances readability despite the length.

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 no parameters and no output schema, the description is remarkably complete. It explains what the tool returns (transform types and schemas), what it excludes (components), provides a 5-step usage process, and specifies when to call it relative to the RL workflow.

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 tool has zero parameters, so the baseline is 4 per the rubric. The description mentions that it returns lists like valid_transform_types and transform_parameter_schemas, but since there are no params to explain, this is sufficient.

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 clearly states that the tool returns a scoring-function design guide with authoritative transform schemas from the live REINVENT registry. It distinguishes itself from siblings by explicitly noting it does not define component names/params, and by positioning itself as the source of truth for transforms.

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 provides explicit when-to-use guidance: 'Call this before reinvent_reinforcement_learning to collect the scoring config.' It also states alternatives (component registry for components, /custom-component routing) and prohibitions ('Never use a transform type not in this list').

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