gitea_list_organizations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions 'current authenticated user' indicating auth scope, it fails to disclose pagination behavior (despite having page/limit parameters), return format, or rate limiting characteristics.

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 brief and front-loaded, but includes the '[UNIFIED]' metadata tag which appears to be non-semantic noise. Given the complete lack of schema documentation, the description is overly terse rather than appropriately concise.

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 zero schema descriptions, no annotations, and no output schema, the description is insufficient for reliable use. It omits critical context such as the meaning of the required 'site' parameter and the structure of the returned organization data.

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 parameters (site, page, limit). The description completely fails to compensate by explaining that 'site' refers to the Gitea instance identifier, or that page/limit control pagination of results.

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 identifies the verb (List) and resource (organizations) and specifies the auth-scoped context (for the current authenticated user). However, it does not explicitly distinguish from sibling tool `gitea_get_organization`, which retrieves a specific organization by identifier versus listing all organizations for the user.

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_get_organization`, nor does it mention prerequisites such as authentication requirements or when pagination is necessary.

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