github_enterprise_team_memberships_get

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

No annotations are provided, and the description only says 'Get', implying a read operation. It fails to disclose permissions needed, error behavior (e.g., not found), or response format. Since annotations are absent, the description should carry the full burden of behavioral context but does not.

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 a single sentence, which is concise but lacks necessary detail. It is not structured, but it avoids verbosity. However, conciseness without completeness is a trade-off that reduces effectiveness.

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 has three required parameters, no annotations, and no output schema, the description is incomplete. It does not describe the return value (e.g., membership status, role) or error conditions. Without output schema, the description should cover what the tool returns, which it fails to do.

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?

Input schema descriptions are merely the parameter names ('enterprise', 'enterprise-team', 'username') with no added meaning. The tool description does not clarify what these parameters represent (e.g., org slug, team slug, GitHub username). Schema coverage is 100% but adds no value beyond stating existence.

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 'Get enterprise team membership' uses a clear verb and resource, indicating a retrieval operation. However, it does not specify that it retrieves membership for a specific user, which is implied by the username parameter but not stated. It distinguishes from sibling tools like 'list' (which returns all memberships) but lacks explicit differentiation.

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 on when to use this tool versus alternatives like 'list', 'add', or 'remove'. The description does not state that it is for checking a single user's membership status or contrast with other membership operations.

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