assign_issue

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

No annotations are present, so the description carries the behavioral burden. It usefully discloses that assignees are verified first and unverifiable users are rejected rather than guessed. However, it does not state whether assignment replaces existing assignees, what permissions are required, or how partial failures are handled.

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?

Two concise sentences with no filler. The core action is front-loaded, and the important verification behavior is stated immediately after, earning its place.

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 description covers the core purpose and a key validation behavior, and an output schema exists to document return values. Still, for a mutating operation with no annotations, it omits important context such as whether existing assignees are replaced or appended, permission prerequisites, and partial-failure behavior.

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 adds meaning for assignees by specifying 'one or more' and describing verification behavior, but it does not explain owner, repo, or issue_number. Those parameters are self-explanatory in a GitHub context, so the gap is moderate.

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?

States a specific action ('assign') and object ('one or more GitHub users'), which clearly distinguishes it from sibling tools that get, search, label, comment on, close, or reopen issues. The target issue is implied by the tool name and the required issue_number parameter, so meaning is unambiguous.

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 explicit guidance about when to use this tool instead of siblings such as add_labels or post_comment, and no exclusions or alternative conditions. The usage context is only implied by the tool name and the action itself.

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