Post Collection Comment / Reply

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

Annotations already signal this is a write operation. The description adds useful behavioral context by stating it 'Uses the site's CreateComment mutation with the web session', which discloses the implementation mechanism and an authentication prerequisite. No contradiction with annotations.

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 concise sentences deliver the core purpose and the key implementation detail with no filler. The purpose is front-loaded, and every phrase earns its place.

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 simple write operation with no output schema, this description is adequate but not complete. It omits any mention of what the tool returns on success or failure, and does not explicitly state whether replies require comment_thread_id as well, leaving some uncertainty for an agent.

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 0%, so the description is the only source of parameter meaning. It clarifies that comment_thread_id comes from get_collection and that reply_to_id is used for replies, but it leaves body's role implicit and does not explain the relationship between reply_to_id and comment_thread_id in a reply scenario.

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 verb and resource: 'Comment on a collection' or 'reply', and even names the source of the comment_thread_id (get_collection). This clearly distinguishes the tool from post_mod_comment and other collection-related 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?

It explains when to use the tool: to comment on a collection or reply to an existing comment, and identifies where comment_thread_id comes from. However, it does not explicitly exclude alternatives like post_mod_comment or edit_collection_comment, so the guidance is clear but not fully exhaustive.

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