github_issues_check_user_can_be_assigned_to_issue

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

The description implies a read-only operation ('Check'), but with no annotations and no explicit statement about side effects, the agent cannot be certain it does not modify state. No details on authentication, rate limits, or error behavior are provided.

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 brief but contains a grammatical error ('a issue'). It conveys the core function but could be more polished and 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 lack of annotations and absence of an output schema, the description should at least indicate the return type (e.g., boolean) or response structure. It does not. The tool's behavior and expected output are under-specified for an AI agent to reliably invoke.

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?

All four parameters have descriptions that merely repeat the parameter name (e.g., 'owner' described as 'owner'), adding no semantic value. The description itself does not elaborate on parameter meaning or constraints.

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 states a specific verb and resource: 'Check if a user can be assigned to a issue.' It clearly indicates a permission check before assignment, which distinguishes it from assignment mutation tools like add_assignees. However, the grammatical error and lack of differentiation from the similar sibling tool 'github_issues_check_user_can_be_assigned' slightly reduce clarity.

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 provided on when to use this tool versus alternatives (e.g., the similar sibling tool, or when to use add_assignees). There is no mention of prerequisites, context, or conditions that would inform tool selection.

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