post_to_social

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

No annotations are provided, so the description carries the burden. It discloses that it returns per-platform results, and mentions optional photo/video. It does not contradict any annotations (none exist). It does not detail side effects or permissions, but for a post tool the behavior is fairly 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?

Two sentences with no wasted words. First sentence defines the action and optional media, second gives the prerequisite and return value. Efficient and easy to parse.

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?

The description covers the main action, optional media, prerequisite, and return structure. However, it lacks details on error handling, platform validation, or what happens if a platform is not connected. Given no output schema and no annotations, a bit more context would be beneficial.

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 baseline is 3. The description adds that photo/video are optional and that it uses PostWire, but does not provide additional detail on parameter formats or constraints beyond what the schema already says.

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 verb (Publish), resource (post), and scope (to one or more social platforms via PostWire). It distinguishes from the sibling tool list_platforms, which is for listing available platforms, not posting.

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 explicitly mentions a prerequisite: connecting accounts at the provided URL. It implies usage for publishing posts, and the sibling tool list_platforms complements it. However, no explicit when-not-to-use or alternative scenarios are given.

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