Github Set Assignees

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description does not need to repeat those. However, the description adds no further behavioral context such as whether setting an empty array clears assignees, whether existing assignees are replaced or appended, or what permissions are required. Given this is a mutation tool, the lack of added behavioral detail is a noticeable gap.

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 brief with the core purpose front-loaded in the first sentence. The second sentence is a concise pointer to a skill for workflow, adding some utility without excessive verbosity. It earns its place, though it could be more self-contained.

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?

With 4 required parameters, no schema descriptions, and only a sparse description, an agent lacks critical context for correct invocation: valid values for assignees (e.g., GitHub usernames), whether the array replaces all assignees, and the exact meaning of issue_number. Although an output schema exists, the description is incomplete for a mutation tool with this complexity.

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 for the undocumented parameters. It mentions 'assignees' and 'issue or pull request' but does not explain the meaning or format of repo_owner, repo_name, issue_number, or the assignees array contents. The description adds minimal value beyond the parameter names already present in the schema.

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 clear verb and resource: 'Updates the assignees for a specific issue or pull request.' It identifies the target resource as an issue or PR, which is unambiguous. However, it does not explicitly differentiate itself from sibling tools like github_set_issue_milestone or github_set_pr_draft.

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 implies when to use it: whenever assignees need to be updated on an issue or PR. It references a skill 'pr-management' for workflow, but gives no explicit guidance on when not to use this tool or what alternatives exist. This is minimal but not misleading.

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