create_publishing_post

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

With no annotations provided, the description carries full burden. It discloses that the post is scheduled for a future time and appears in a calendar, but omits behavioral traits like authentication requirements, rate limits, idempotency, or whether the operation is reversible (e.g., can be deleted). Partial but insufficient.

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?

Two sentences succinctly convey purpose and key context without filler. The description is front-loaded with the primary action and resource. Every word earns its place.

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 6 parameters (3 required), no output schema, and sibling tools including 'get_publishing_post', the description is minimally complete. It explains the tool's purpose and scheduling nature but does not describe the return value (e.g., post ID) or explicitly tie to 'upload_media' despite the parameter reference. Adequate but with gaps.

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 each parameter. The description adds only minor context ('future time' aligns with scheduled_time) but does not clarify parameter meaning beyond what's in schema. Baseline 3 is appropriate.

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 clearly states the action 'Create a new publishing post', the resource ('a publishing post in Sprout Social'), and key context ('to be published at a future time', 'appear in Sprout's publishing calendar'). It effectively distinguishes from the sibling tool 'get_publishing_post', which retrieves existing posts.

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 implies use for scheduling future posts but does not explicitly state when to use this tool versus alternatives (e.g., for immediate posting, if supported). It also lacks guidance on prerequisites, such as needing to upload media first via 'upload_media' (referenced in schema).

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