zuckerbot_tag_creative

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

The description discloses the mechanism (Claude vision analysis, storage) and data flow (feeds creative_analysis pipeline). With no annotations provided, the description carries full burden. It does not mention permissions, rate limits, or side effects, but the mutation nature is implied by 'tag'. Adequate but not comprehensive.

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 very concise: three sentences that cover purpose, method, downstream use, and timing. Every sentence adds value with no repetition or fluff.

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 tool has no output schema, and the description does not mention return values or output behavior. It explains the stored tags and pipeline but not what the function returns to the caller. Considering the complexity (nested objects in input), the description leaves a gap in expected output.

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 coverage is 100%, so the baseline is 3. The description adds context about using Claude vision with asset URLs, but this is already implied by schema parameter descriptions. No additional meaning beyond what the schema provides.

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 the action ('Tag Meta ads'), the resource, and specific attributes (hook type, visual style, etc.). It also mentions the use of Claude vision and differentiates from sibling tools like 'zuckerbot_creative_analysis' by noting that this tagging feeds that pipeline.

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 timing advice ('Run this after launching new ads'), which helps the agent decide when to invoke. However, it does not mention when not to use the tool or suggest alternative tools, which would strengthen guidance.

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