gitea_list_issue_comments

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

No annotations are provided, so the description carries the full burden. It only implies a read-only operation via the verb 'List' but provides no details about pagination, rate limiting, authentication requirements, or whether system-generated comments are included.

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. The '[UNIFIED]' prefix appears to be metadata noise that doesn't add value, but the core statement is appropriately brief and front-loaded.

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 4 required parameters with zero schema documentation and no annotations or output schema, the description is inadequate. It fails to explain the parameter semantics or behavioral traits necessary for an agent to correctly invoke this tool without guessing parameter meanings.

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 0% for all 4 parameters (site, owner, repo, issue_number). The description fails to compensate by explaining what 'site' refers to (Gitea instance URL), what 'owner' means (user/organization), or the expected format of any parameters.

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 clearly states the tool lists comments on an issue. The phrase 'on an issue' effectively distinguishes this from the sibling tool `gitea_list_pr_comments` (which handles pull requests), though it could specify this is for Gitea issues explicitly.

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 versus alternatives like `gitea_create_issue_comment` or `gitea_list_issues`. No mention of prerequisites such as requiring valid credentials for the specified site.

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