postfader_review_record_feedback

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

The description adds a meaningful behavioral rule beyond the annotations: 'silence and measurements never grant approval.' This clarifies that the tool won't infer approval from indirect signals and that explicit verdicts are the only approval source. Combined with readOnlyHint=false, the write nature is understood, though no details about side effects or locking are given.

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 a single, dense sentence that front-loads the core purpose and an essential constraint. Every word earns its place; there is no filler or repetition.

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 a large and complex schema, the description is sparse but covers the most critical behavioral rule. It doesn't explain what the recorded feedback is used for or how it fits into the postfader review workflow, but the schema and sibling tool names supply much of that context. Adequate but not rich.

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 schema description coverage is 100%—the single 'feedback' parameter and its nested types are fully described in the schema, including the phrase 'Explicit structured producer feedback and independent locks.' The tool description adds only the word 'explicit', which aligns with the schema but doesn't provide new semantic meaning.

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 states a clear action ('Record') and resource ('explicit feedback'), which conveys the primary behavior. It includes a distinguishing constraint—'silence and measurements never grant approval'—but relies on the tool name to identify the 'creation review' scope, so it doesn't strongly differentiate from sibling tools like sound_selection_record_feedback.

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 implicitly gives usage guidance: only explicit feedback should be recordedapsing, and silence/measurements should not be used as a basis for approval. This tells the agent when not to use the tool, though it doesn't explicitly name alternatives or describe the exact workflow context in which this should be invoked.

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