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

Goes well beyond the annotations: declares async execution, credit spend backed by creditsReserved with refund-on-failure, a 10 packs/hour rate limit, the jobId return and polling contract, and a ~2 minute minimum completion time. This is unusually rich disclosure for a mutation tool whose destructiveHint/openWorldHint annotations only sketch the risk profile.

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?

Long but front-loaded, with the async nature and personality scoping stated first and operational facts (credits, rate limit, polling cadence) grouped after. Every sentence carries load, though the parenthetical onboarding note and capped emphasis could be tightened.

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?

With no output schema, the description carries the return contract itself (jobId, poll get_influencer_snack until 'completed') plus latency and error behavior, so an agent has everything needed to call and follow up correctly.

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 100%, so the schema already documents count, types, exclude, prompt and influencerId. The description adds no per-parameter syntax or defaults, so the baseline of 3 applies.

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?

States a specific verb and resource ('generate an ASYNC snack content pack in the voice of a specific influencer') and explicitly distinguishes itself from the brand-scoped sibling generate_snacks. The parenthetical mapping to the '+ New content' UI action further disambiguates it.

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?

Gives explicit when-to-use context (influencer-scoped generation), removes a common blocker ('you do NOT need to attach a brand first'), states the only failure condition, and names the alternative sibling it is scoped against.

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