capture_backlog

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

Adds real behavior beyond annotations: the required item.add and item.update_status permissions before any mutation, and the concrete no_change outcome for already-Backlog items. Annotations already cover safety/idempotency hints, but the description usefully restates idempotency in terms of a specific observable result.

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 sentences, front-loaded with the primary action and outcome, then permissions. No filler; every clause carries information an agent needs.

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?

No output schema exists, and the description covers the key return signal (no_change) and the permission prerequisites. It is nearly complete for a 3-param mutation, though it leaves the meaning of number and the exact capture mechanics (create vs. link existing item) unstated.

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 carry parameter meaning. It partially does: url is implied to be the Issue/PR URL and owner is implied to be the Project owner ('one authorized Project'), but the required number parameter is never explained, and none of the three params are explicitly defined.

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 verb (capture) plus resource (GitHub Issue/PR URL) and the exact resulting state ('Status is exactly Backlog'). This distinguishes it from the generic sibling add_github_project_item, which implies adding an item without forcing a status.

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?

Usage is implied by the stated outcome (capture into Backlog) and the idempotent 'returns no_change' case is described, but no alternatives such as add_github_project_item or update_github_project_item_status are named, nor is when-not-to-use specified.

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