gitea_list_issues

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

No annotations provided, so description carries full burden. Mentions 'paginated' but omits page size limits, rate limiting, or default sort order. 'Filters' mentioned without explaining filter syntax (e.g., comma-separated labels) or behavior.

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?

Two sentences, efficiently structured. However, the '[UNIFIED]' prefix appears to be metadata noise rather than useful content. Given the complete lack of schema documentation, the brevity becomes under-specification rather than clarity.

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?

Tool has 8 parameters including pagination and filtering, no output schema, and no annotations. Description insufficient for this complexity level—missing filter semantics, pagination details, return structure, and error conditions.

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 has 0% description coverage, requiring the description to compensate. It fails completely—'q' parameter meaning unexplained, 'state' values unspecified, 'labels' format (array vs comma-string) not documented, and 'site' parameter purpose unclear.

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?

States specific action ('List issues') and resource ('Gitea repository') clearly. Mentions 'filters' and 'paginated' to clarify scope. However, fails to distinguish from sibling tool 'gitea_get_issue' which retrieves a single issue versus listing multiple.

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?

Provides no guidance on when to use this tool versus alternatives like 'gitea_get_issue' for single issue retrieval or search strategies. No mention of prerequisites like authentication requirements or permissions needed.

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