Gitea: Create issue comment

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — it does not warn that non-idempotent retries can create duplicate comments, nor mention permissions or return behavior, which is the useful context it could have supplied.

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?

It is a single short sentence with no padding, which is good, but the bracketed "[UNIFIED]" marker is unexplained and the brevity comes at the cost of substance. Conciseness here reads as under-specification rather than efficiency.

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?

A five-required-parameter mutation tool with no output schema and zero schema coverage needs far more than one sentence. Nothing explains the site parameter, the body format, or what the call returns (e.g., comment ID), leaving an agent to guess on required inputs.

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?

All five parameters (site, owner, repo, issue_number, body) have 0% schema description coverage, so the description carries the full burden of explaining them and says nothing about any. It is impossible to tell from the definition what "site" means (host/instance?) or what format body accepts.

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 ("Add a comment to an issue"), so an agent knows the basic operation. It does not differentiate from the very similar sibling gitea_create_pr_comment, and the "[UNIFIED]" prefix is unexplained noise that adds no selection value.

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?

There is no guidance on when to use this versus gitea_create_pr_comment, gitea_list_issue_comments, or gitea_update_issue, and no prerequisites (e.g., issue must exist, must be open) are mentioned. The only implicit cue is the word "issue".

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