Create comment

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

No annotations exist, so the description carries the full burden. It discloses the scheduling behavior (omit for immediate, parentCommentId for reply) and that this is a creation action, but it does not address side effects, failure modes, authentication, or return values.

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 entire description is one sentence, front-loading the core action and then adding the two optional-behavior clauses without padding.

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 5-parameter mutation with no annotations or output schema, the description covers the primary behavior and optional modes, but lacks details on response, error conditions, and constraints on posting (e.g., cannot reply to non-scheduled comments).

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 only 40%; the description compensates by explaining the two most ambiguous parameters: scheduledAt controls immediate vs. scheduled publishing, and parentCommentId enables replying to a scheduled comment. postId and text are self-explanatory and accountId already has a schema 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?

Description opens with a specific verb-resource pair ('Create a comment on a post') and clarifies the acting account. It further distinguishes the scheduling and reply modes, setting it apart from post-creation and comment-edit siblings.

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 explains when to omit scheduledAt (immediate publish) and when to pass parentCommentId (reply to a scheduled comment). While it doesn't explicitly name alternative tools like update_comment or delete_comment, the context is clear enough for tool selection.

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