reply_to_post

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

Discloses that it creates a threaded reply and requires authentication, which is helpful, but no annotations exist and it omits details on side effects, errors, or rate limits.

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 that are concise, front-loaded, and directly address the tool's core purpose and a key requirement (authentication).

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?

Despite low schema coverage and no annotations, the description is too brief, lacking details on parameter formats, return values, error handling, and behavioral specifics for a mutation tool with four parameters.

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?

With 0% schema description coverage, the description provides no explanations for the parameters (text, root, parent, langs); it only vaguely mentions 'parent/root references' without clarifying differences.

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 clearly states the action (reply), the resource (existing post), and the threading behavior (proper parent/root references), distinguishing it from siblings like create_post.

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?

Mentions authentication requirement but fails to specify when to use this tool versus alternatives like create_post for top-level posts, leaving it implied rather than explicit.

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