github_list_org_members

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'List members', which implies a read operation but does not explicitly state read-only, authentication requirements, pagination behavior, or side effects. No details about handling invalid orgs or partial results are given.

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 concise with a one-sentence purpose followed by a clear Args block. Every word earns its place, with no fluff or repetition. It front-loads the primary purpose and then lists parameter semantics in a structured way.

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?

The tool is simple and has an output schema, so return values are already covered. However, the description omits behavioral context such as whether the session is optional (schema shows default 'default' but description doesn't mention it), whether it lists public or all members, and any authentication prerequisites. Given zero annotations, these gaps leave the agent underinformed.

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%, so the description must compensate. It does by explaining each parameter: 'org: Organization name', 'max_results: Maximum members to return (default: 50)', and 'session_name: GitHub session to use'. These add meaning beyond the bare schema titles, though session_name's meaning remains somewhat vague.

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 'List members of an organization' uses a specific verb ('List') and resource ('members of an organization'), which clearly distinguishes it from sibling tools like github_list_repos or github_list_org_repos. It is not a tautology because it adds the qualifier 'of an organization' and is unambiguous in its intent.

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 is given on when to use this tool versus alternatives. The description merely states what it does, but does not mention exclusions (e.g., 'use github_get_user for user details') or prerequisites (e.g., 'requires org membership') to guide an agent's decision-making.

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