Social Post Comment

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

With no annotations provided, the description carries the full transparency burden and does so well: it discloses the session requirement, rate-limit behavior, and spam/disallowed-content rejection with the resulting CommentPostFailure. This is meaningful operational context beyond the name and schema.

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 four concise, purposeful sentences with the core action first, followed by auth requirements, rate-limit failure caveats, and sibling routing. No filler or duplication of schema content.

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?

Given a complete input schema and an output schema, the description covers the critical external context an agent needs: authentication, failureprone behavior, and which sibling to prefer for replies. The most operationally relevant sibling is named, and nothing essential is missing.

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 input schema already documents all 5 parameters including enums, formats, and defaults. The description does not need to restate parameters, and since it adds no additional param-level meaning, the baseline score of 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 states a specific action and resource: posting a comment to a project, studio, or user profile as the active session. It distinguishes itself from the key sibling social_reply_to_comment, so an agent can tell top-level commenting apart from replying.

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?

It explicitly names the alternative social_reply_to_comment and instructs to prefer it when replying to an existing comment. It also states the prerequisite of a logged-in session, giving clear when/when-not guidance.

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