zuckerbot_launch_portfolio

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

No annotations exist, so the description is responsible for behavioral disclosure. It honestly states the tool is unavailable and will not create Meta objects, which prevents an agent from assuming side effects. It does not explicitly describe failure modes, but the unavailability warning is transparent.

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 critical status 'Not currently available' is front-loaded, and the alternative guidance is delivered in two tight sentences with no wasted words.

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 that is unavailable, this is complete: it tells the agent not to call it, gives the alternative, and mentions legacy-mode drafting. The only small gap is that 'legacy-mode draft' is not further described, but the referenced launch_campaign path covers the action.

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 parameters are already documented. The description adds no parameter-level detail, which is acceptable here because the tool is unavailable and existing parameter descriptions suffice.

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 says 'Not currently available' and that new multi-tier launches do not create Meta objects, but it never directly states what the tool is or was for. Its intended function is only implied by the tool name and schema.

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?

Explains exactly when not to use this tool and points to an explicit alternative: 'use zuckerbot_launch_campaign for the supported live path.' Also notes that portfolio planning and monitoring remain available, helping the agent route to the right tool.

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