gitea_create_pr_comment

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

No annotations are provided, yet the description fails to disclose critical behavioral traits: whether this creates a top-level comment vs review comment, error handling for non-existent PRs, idempotency, or that it performs a write operation.

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?

Consists of a single sentence with no wasted words, achieving brevity. However, it is underspecified for the tool's complexity (5 undocumented parameters), falling short of being 'appropriately sized'.

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?

Completely inadequate for a 5-parameter write operation with zero schema documentation, no output schema, and no annotations. The description provides only the basic operation name without sufficient context to use the tool correctly.

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 required parameters, the description must compensate but adds no semantics. Critical fields like 'site' (Gitea instance URL?), 'owner' (user vs org?), and 'body' format remain completely undocumented.

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 'Add a comment to a pull request,' which identifies the specific verb (add) and resource (PR comment). However, it fails to distinguish from siblings like `gitea_create_issue_comment` (issues vs PRs) or `gitea_create_pr_review` (reviews vs comments), and the '[UNIFIED]' prefix adds no semantic 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?

No guidance provided on when to use this tool versus alternatives like `gitea_create_issue_comment` or `gitea_create_pr_review`, nor any mention of prerequisites such as the PR existing or required permissions.

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