zuckerbot_create_portfolio

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

With no annotations, the description carries the full behavioral burden and does provide meaningful disclosure: portfolios are planning/monitoring-only, launch is unavailable, and budgets are split into prospecting, retargeting, and reactivation tiers with per-tier CPA targets. It does not cover response shape or edge cases, but the major operational constraint is clear.

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 compact, front-loaded with the core action, and every sentence adds either scope, supported source, or a key limitation. There is no redundant or filler content.

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?

Given no annotations and no output schema, the description gives sufficient context for an agent to understand the tool's purpose, constraints, and behavior, including the critical no-launch limitation. It also explains how tiers and budgets work so the agent can reason about the 7 optional parameters.

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 value by explaining how the parameters relate: a total budget is split across tiers using percentages, and CPA targets apply per tier. It also clarifies the template vs custom tier selection model, going beyond the raw field names.

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 and resource: create a portfolio, and qualifies it as multi-tier, audience-based, planning/monitoring-only, and sourced from a template or custom array. This clearly distinguishes it from sibling portfolio tools like get_portfolio, update_portfolio, rebalance_portfolio, and launch_portfolio.

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?

It gives clear context: the agent should use this tool to create a planning/monitoring portfolio and explicitly says portfolio launch is not currently available, avoiding incorrect expectations. It does not explicitly name sibling alternatives, but the create-versus-manage distinction is strongly implied.

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