get_project_members

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. It adds useful context: it specifies that the tool retrieves both user and group memberships and supports pagination, which are behavioral traits not inferable from the schema alone. However, it lacks details on permissions, rate limits, error handling, or response format, leaving gaps for a read 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 highly concise and front-loaded: the first sentence states the core purpose, and the following two sentences add essential behavioral details without redundancy. Every sentence earns its place by providing distinct value, making it efficient and well-structured.

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 tool's moderate complexity (3 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the purpose and key behaviors (membership types, pagination), but lacks details on response format, error cases, or usage context. This makes it adequate for basic understanding but insufficient for full agent guidance without additional context.

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 schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'Supports pagination,' which implicitly relates to the limit and offset parameters, adding some semantic meaning. However, it doesn't explain the project_id parameter or provide details on pagination behavior (e.g., default values), so it partially compensates but not fully, aligning with the baseline for moderate coverage.

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 tool's purpose: 'Get members and their roles for a specific project in Lychee Redmine.' It specifies the verb ('Get'), resource ('members and their roles'), and scope ('for a specific project'), distinguishing it from siblings like get_users (general users) or get_project (project details). However, it doesn't explicitly differentiate from all siblings (e.g., get_projects might imply member info), keeping it at 4 rather than 5.

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. It mentions 'Includes user and group memberships' and 'Supports pagination,' but these are behavioral details, not usage instructions. There is no mention of prerequisites, when to choose this over get_users or get_project, or any exclusions, resulting in minimal guidance.

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