Kommentar löschen

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

No annotations are provided, so the description must disclose behavioral traits itself. It only says 'deletes a comment' without explaining that the 'force' parameter controls permanent deletion vs. trash, or what happens to the comment, permissions needed, or return behavior. The schema partially covers the force parameter, but the description itself adds no behavioral context.

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 a single, concise sentence that is immediately understandable. It is front-loaded and contains no unnecessary words. However, it is arguably too terse, omitting valuable context that could be included without bloat.

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 no annotations, no output schema, and a potentially destructive operation, the description is incomplete. It fails to mention the trash vs. permanent-delete behavior (only in schema), the return value, or any caveats. For a delete tool, more context is needed for safe and correct usage.

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 parameters are already well-documented (commentId as number, force as a permanent-delete flag). The description adds no additional meaning beyond the schema, but since the schema is complete, a baseline 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 'Löscht einen Kommentar' clearly states the action (delete) and resource (a comment), matching the tool name. It is specific and unambiguous, but it does not explicitly differentiate from sibling tools like comment_moderate_bulk, which could also involve removal actions in a bulk context.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or situations where another comment-related tool (e.g., comment_update, comment_moderate_bulk) would be more appropriate.

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