github_orgs_check_public_membership_for_user

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 only states the action without indicating the return type (e.g., boolean), side effects, or that it is a safe read operation. Missing details on what 'check' entails.

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 concise sentence, front-loaded with the key action. It is efficient with no wasted words, though it could benefit from additional context without becoming verbose.

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 that there is no output schema, the description should at least hint at the response format (e.g., boolean, message). It does not provide any information about the return value or behavior. The description is too minimal for a tool that requires clarity on what 'membership' status is returned.

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?

Although schema coverage is 100%, the parameter descriptions in the schema are tautological (just 'org' and 'username'). The tool description adds no extra meaning about the parameters, such as expected format or examples. Schema coverage does not compensate for the lack of semantic enrichment.

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 'Check public organization membership for a user' clearly states the verb 'Check', the resource 'public organization membership', and the target 'user'. It distinguishes from sibling tools like github_orgs_check_membership_for_user (private membership) and github_orgs_list_public_members (list all).

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 such as github_orgs_check_membership_for_user or github_orgs_list_public_members. It does not specify that this is for public membership only, nor does it mention any prerequisites or exclusions.

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