publish_social_post

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

No annotations are provided, so the description carries all responsibility for behavioral disclosure. It notes the confirmation prerequisite but omits side effects (e.g., publishing publicly), error states, or whether navigation happens. The post-click outcome is entirely undisclosed.

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, front-loaded with the action and confirmation requirement. No fluff. The core instruction is clear and quick to scan.

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?

Without an output schema or annotations, this tool leaves out success/failure behavior, prerequisites like being logged in or on the right tab, and how to obtain publishButtonRef. Minimal description for a side-effectful action.

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 coverage is low (only 'confirmed' has a description). The tool description adds little beyond restating the confirmed requirement, and does not explain publishButtonRef (presumably a selector) or tabId (which page). Agents can't infer correct values from the description.

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 action (click a publish button) on a social site, distinguishing it from generic click and draft_social_post siblings. However, it doesn't explicitly name these alternatives, so the differentiation is implied rather than stated.

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?

Provides a usage condition: 'Requires confirmed=true after the user has reviewed the draft.' This tells when the tool can be invoked, but it doesn't mention when not to use it, what prior steps are needed, or when the alternative draft_social_post or click should be used instead.

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