gitea_list_labels

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to state whether this operation is read-only (implied by 'List' but not explicit), whether results are paginated, or what happens when the repository doesn't exist. No rate limits, auth requirements, or error conditions are documented.

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 appropriately brief at one sentence, but includes the '[UNIFIED]' prefix which appears to be noise or template metadata rather than useful descriptive content. The core information is front-loaded but diluted by the unexplained tag.

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 the absence of an output schema, the description should indicate what data structure or fields are returned (e.g., label names, colors, IDs), but it does not. Combined with completely undocumented parameters, the description provides insufficient context for reliable invocation despite the operation's conceptual simplicity.

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?

The input schema has 0% description coverage for its three required parameters (site, owner, repo), and the description adds no compensatory documentation explaining what 'site' refers to (instance URL?), the format of 'owner', or repository naming conventions. This leaves all parameters effectively 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 clearly states the core action ('List') and resource ('labels in a repository'), which distinguishes it from sibling tools like gitea_list_issues or gitea_create_label. However, the '[UNIFIED]' prefix appears to be template metadata or implementation jargon that provides no semantic value to the AI agent and may cause confusion.

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_label, or when label listing is appropriate in a workflow. There are no preconditions, prerequisites, or contextual triggers mentioned.

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