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

Annotations already reveal this is a non-read-only, non-idempotent, open-world write. The description adds substantive behavior beyond them: it discloses platform constraints most writers wouldn't guess, such as media URLs needing to be publicly reachable, Instagram images needing to be JPEG, and stories requiring an Instagram-login account and suppressing captions. It stops short of addressing idempotency/duplicate-post risk or rate limits, which matter for a non-idempotent publish.

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?

Front-loads the action and destination, then packs constraints into parentheticals. It is dense with parenthesis-heavy asides, but each clause carries actionable platform detail rather than filler, so little is wasted.

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 write tool with no output schema, the description covers the parameters, platform rules, and channel-id prerequisites needed to call it correctly. It does not describe what a successful call returns (e.g., a post id) or confirm duplicate-post behavior, minor gaps against a mutation tool.

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?

With 75% schema coverage the baseline is already 3, and the description adds real meaning beyond the schema: it explains that multiple media items form an Instagram carousel, that 'story' publishes a single image/video with no caption, and it restates the URL reachability and JPEG constraints. The 'text' and 'id' parameters are only lightly touched, but the enum parameter is well covered.

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?

States a specific verb ('Publish') and resource ('one of the organization's connected social accounts') and distinguishes itself from the many sibling post/send tools by scope. It even names the sibling (neuron_list_social_channels) that supplies the channel id, so the agent can place it in the workflow without opening a 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?

Gives clear when-to-use context: obtain the id from neuron_list_social_channels, use as='story' for Instagram stories, and rely on carousel behavior when several media items are provided. It does not explicitly contrast with neuron_post_to_newsletter or neuron_post_to_status, but the 'connected social account' framing makes the domain clear.

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