Post Mod Comment / Reply

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

Annotations already indicate a non-read-only, non-idempotent, non-destructive operation. The description adds meaningful behavioral context: a logged-in web session is required and BBCode is allowed. This goes beyond the annotations, though it stops short of explaining error handling or visibility outcomes.

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 with zero filler. Each sentence carries distinct value: the core action, the reply mechanism, the session requirement, and formatting info. Everything is front-loaded.

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 write operation with no output schema, the description provides the essential invocation details: what to post, where, how to reply, auth, and formatting. It does not mention return values, but that is not critical when no output schema exists.

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 50%; the schema describes game and parent_id but not text or mod_id. The description compensates by explaining that parent_id is the comment id from get_mod_comments and that BBCode is allowed in text. mod_id is left undocumented, but it is relatively self-evident in context.

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 uses a specific verb ('Post') and resource ('comment on a mod's Posts tab'), and clearly covers the reply case by referencing parent_id from get_mod_comments. This distinguishes it well from siblings like post_collection_comment and forum_reply.

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 clearly states where to post (mod's Posts tab) and how to reply (using parent_id from get_mod_comments), and it notes the auth prerequisite. It does not explicitly name alternatives or say when not to use it, but the context is sufficiently clear for an agent to select it.

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