tdarr_transcode_user_verdict

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

With no annotations, description fails to disclose what 'take action' means—e.g., whether it deletes, approves, or modifies the item. No indication of side effects or required permissions.

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?

Extremely short but wastes the opportunity to inform; one sentence conveys little. Could be rewritten to pack more meaning.

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?

Massively incomplete: no output schema, no annotations, and with many sibling tools, the description should clarify prerequisites, expected file state, and outcomes. Currently useless for an agent.

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?

Description adds no meaning beyond schema; 'verdict' is only described in schema as 'accept/reject', and 'obj' is just 'File object'. No clarification on required fields or acceptable values.

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?

Description 'Take action on a staged item' is vague; does not specify that the action is a verdict on a transcode, which is implied by the tool name. Slightly better than tautology but lacks specificity.

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?

No guidance on when to use this tool versus alternatives like tdarr_search_flow_plugins or tdarr_scan_file. Missing context about staging workflow.

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