publish_marketing_email

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 so well. It discloses that the action cannot be recalled, that the recipient list is defined in HubSpot rather than by the caller, that it is the most consequential tool, and that lower tiers will fail with a 403 that should not be worked around. This goes far beyond the bare 'send' verb.

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 front-loaded with the action, then uses the remaining sentences for high-value safety and prerequisite information. It is longer than average, but every sentence earns its place for a consequential, irreversible tool, and the structure clearly separates action, warning, and licensing context.

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 the tool's high stakes and absence of annotations, the description is nearly complete: it covers purpose, workflow, irreversibility, recipient-list ownership, licensing, and error behavior. The main gap is the lack of explicit user_confirmed parameter semantics, which is important enough to prevent a perfect score even though the workflow strongly implies it.

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 0%, and the description never directly names or explains email_id or user_confirmed. It indirectly implies that email_id corresponds to the email retrieved via get_marketing_email, and the warning to ask the user before sending gestures at the confirmation requirement, but it leaves the precise role of user_confirmed and the effect of false unexplained.

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 opens with a specific action and object: 'Send a marketing email, or schedule it per its own settings.' This clearly distinguishes the tool from sibling publishing tools like publish_page and publish_blog_post by naming the marketing-email resource, and from unpublish_marketing_email by the opposite action.

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 gives a clear before-use workflow: read the email with get_marketing_email, tell the user what it is and who it goes to, and get confirmation before invoking. It also states the licensing constraint and the 403 billing-boundary behavior. It does not explicitly name alternative tools or when-not-to-use conditions, but the resource and context make the intended use clear.

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