gitea_create_issue_comment

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

No annotations are provided, so the description must carry the full burden. While 'Add' implies a creation operation, the description lacks details about idempotency, authentication requirements, rate limits, or what happens if the issue doesn't exist. It doesn't clarify whether the operation is destructive or reversible.

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 brief (one sentence), but the '[UNIFIED]' prefix appears to be metadata leakage rather than useful content, slightly diminishing the signal-to-noise ratio. The core message is front-loaded but minimal.

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 this is a mutation operation with 5 undocumented parameters and no output schema, the single-sentence description is inadequate. It lacks context about return values, error handling, or the scope of the created comment.

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 across 5 parameters (site, owner, repo, issue_number, body), the description completely fails to compensate. It provides no information about parameter formats, valid values for 'site', or that 'issue_number' refers to an existing issue ID.

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 clear verb ('Add') and resource ('comment to an issue'), distinguishing it from issue creation or management. However, the '[UNIFIED]' prefix is metadata noise that doesn't add value, and the description doesn't differentiate from sibling tools like gitea_create_pr_comment.

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 like gitea_create_pr_comment or gitea_list_issue_comments. It doesn't mention prerequisites (e.g., the issue must exist) or error conditions.

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