gitea_get_repository

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

With no annotations provided, the description carries the full burden. It states 'Returns complete repository information' but provides no specifics about the data structure, rate limits, error conditions (e.g., private repos), or that this is a read-only 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?

The description is appropriately brief with two sentences. However, the '[UNIFIED]' prefix appears to be metadata leakage rather than descriptive content, and the second sentence partially restates the first ('Get details' vs 'Returns...information').

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?

With no output schema and 0% parameter schema coverage, the description should detail what 'complete repository information' includes or what fields are returned. It provides minimal context for a tool requiring three mandatory identifiers.

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 three parameters (site, owner, repo). The description fails to compensate by explaining parameter semantics, formats (e.g., whether 'site' expects a URL or slug), or providing examples. Parameter names are somewhat intuitive but insufficient for ambiguous fields like 'site'.

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 specific verb ('Get') and resource ('Gitea repository'), and the word 'specific' distinguishes it from sibling 'gitea_list_repositories'. It clearly identifies the target entity, though '[UNIFIED]' adds noise without 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 versus 'gitea_list_repositories' or Prerequisites like needing the exact owner/repo names. No mention of required permissions or authentication context.

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