gitea_list_team_members

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

No annotations provided, so the description carries full burden of behavioral disclosure. It fails to indicate this is a read-only operation, describe pagination behavior (despite having page/limit params), explain return structure, or mention rate limiting concerns typical for member enumeration endpoints.

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?

Extremely concise at two sentences/fragments. The '[UNIFIED]' tag wastes space without adding value for tool selection, but the core description is front-loaded and free of redundancy.

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% input schema coverage, the tool requires rich description to explain the pagination model, member data structure, and 'site' parameter usage. The current description is inadequate for the complexity implied by 4 parameters including pagination controls.

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% across 4 parameters. The description only implicitly suggests 'team_id' by mentioning 'team', but provides no semantics for critical parameters like 'site' (Gitea instance URL), or pagination controls ('page', 'limit'). Insufficient compensation for the schema coverage gap.

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 verb ('List') and resource ('members of a team'), making the basic purpose clear. However, the '[UNIFIED]' prefix adds noise without clarifying scope, and it fails to distinguish from similar sibling tools like 'gitea_list_org_teams' (which lists teams, not members) or cross-platform alternatives like 'appwrite_list_team_memberships'.

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, prerequisites (e.g., obtaining a team_id from 'gitea_list_org_teams'), or pagination strategies for large teams. The description is purely declarative without usage context.

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