socials_quick_reply

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

No annotations are provided, so the description carries the full burden. It discloses the UI workflow (opens reply UI, fills text, submits), a platform limitation (YouTube: no media attachments), and a required user confirmation step. This is comprehensive behavioral disclosure for a tool of this type.

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 information-dense yet structured clearly with bold platform labels and a bullet-like semicolon list. Every sentence adds value—platform-specific IDs, workflow, media constraint, and a safety reminder—without redundancy or unnecessary prose.

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 posting action with no output schema, the description covers all essential aspects: what it does, how to derive required IDs per platform, a platform-specific limitation, and a mandatory user-confirmation step. This is sufficient for an agent to invoke the tool correctly in the intended context.

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% and the post_id parameter description already includes the platform-specific instructions. The tool description repeats this information and adds only marginal context like the pinned-tab scope and YouTube media restriction, which doesn't significantly enrich parameter understanding beyond the schema.

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: 'Post a reply in the pinned agent tab' and then breaks down the expected post_id format per platform (X, LinkedIn, YouTube). This makes the tool's purpose unmistakable and distinguishes it from broader tools like socials_engage_post or socials_create_post.

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 explicit source guidance for post_id on each platform (from socials_get_feed, socials_get_page_content) and adds a hard rule to confirm text with the user before posting. It does not explicitly name alternative tools to use instead, but the platform-specific instructions effectively define the appropriate usage context.

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