generate_social_bulk_xlsx_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It reveals that the tool never publishes, defaults output_filename and timezone, strips directory parts from filenames, returns a warnings list for overly long messages, and identifies the most common cause of rejection (account name mismatch).

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 long but densely informative, organized into clear sections with Args, required vs. optional distinction, and return values. Every sentence adds operational value, such as the account-mismatch warning and the fact that the tool never publishes.

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 with three parameters, one required, the description fully covers input semantics, constraints, defaults, output shape, failure hints, and safety expectations. Nothing an agent needs to call it correctly is missing.

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?

The input schema has 0% description coverage, so the description must fully compensate. It does: it defines each posts requirement (account, scheduled_at, message), lists optional fields (link_url, image_url), provides concrete examples, states the 300-post maximum, and explains output_filename and timezone defaults and behaviors.

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: 'Write a HubSpot-format Excel file for scheduling social posts in bulk.' It clearly distinguishes this from the sibling tools, which are mostly list/create/publish operations for pages, blog posts, and emails rather than file generation for social scheduling.

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 explains exactly when to use this tool: since HubSpot has no public social publishing API, this is the supported route, with the subsequent upload path (Marketing → Social → 'Schedule in bulk'). It also clarifies what the tool does not do — it never publishes — and notes that HubSpot previews every post before publication, giving the agent appropriate context for invoking it.

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