record_iteration_feedback

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

No annotations are provided, so the description must carry the behavioral burden, but it only hints that feedback is tied to active hashes. It does not state whether this mutates state, what permissions or active-run prerequisites are required, whether feedback is validated, or what side effects occur.

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?

It is a single sentence with no wasted clauses, so it is concise. However, the sentence is too abstract for the tool's complexity and lacks front-loaded operational clarity.

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?

The output schema helps with return values, but the description remains incomplete for a tool with two required, undocumented parameters and no annotations. It does not give enough context for an agent to confidently invoke it in the iteration 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?

Schema description coverage is 0%, and the description gives no direct explanation of session_path or the feedback_items structure. "User language and visual evidence" loosely suggests feedback content, but session_path is entirely unexplained and feedback_items remains an unconstrained array of objects.

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 uses the abstract verb "Bind" and mentions user language, visual evidence, and active source/run hashes, but it never plainly states that it records iteration feedback. It is relevant to the tool name but does not distinguish it from nearby iteration tools like evaluate_iteration_candidate or start_feedback_iteration.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tools handle related iteration workflows. The description implies a binding/recording action but leaves the triggering conditions entirely to inference.

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