ae_create_review

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

With no annotations, the description must carry behavioral disclosure. It says 'Create a saved review item' but doesn't explain side effects, persistence, whether files are written, what record is created, or what happens on failure. The agent is left guessing about the tool's impact.

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?

Two short sentences with no filler. The core action and object are front-loaded, and the approval-mode context is added as a separate clause. Every word earns its place.

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 4 parameters, nested objects, no output schema, and no annotations, this description is too thin. It omits return behavior, the purpose of plan_path, and any operational caveats. An agent would need the schema and sibling context to use it confidently.

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 only 25%, so the description must compensate. It clarifies that 'frames' are preview frames and 'render' is optional render metadata, which adds value. However, 'plan_path' is completely unexplained and 'comp' only gets a one-word schema description.

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 specific verb ('Create') and resource ('saved review item'), and specifies content ('preview frames and optional render metadata'). It is distinguishable from siblings like ae_list_reviews and ae_decide_review, though it doesn't explicitly name them.

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?

'Approval mode should use this before final delivery' provides clear situational context and implies the tool belongs early in the review/approval workflow. It does not state exclusions or name alternatives, but the context is enough to route an agent.

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