update_github_project_item_status

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description's mention of "idempotency" is largely redundant. It does add useful context beyond the structured data: authorization is required, the write is verified, and there is an actor-aware audit trail. That is meaningful for a mutation tool, but verification and audit are asserted without detail on how they surface.

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 tight sentences with the behavioral guarantees front-loaded after the alias definition. No filler, though the phrase "compatibility alias for the semantic Status write path" is jargon that costs a small amount of clarity.

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?

For a mutation tool whose annotations already cover safety and idempotency, the description adds authorization, verification, and audit context. However, with no output schema and zero parameter coverage, an agent still lacks any indication of what owner/number/itemId reference or what a successful call confirms.

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% across four required parameters, so the description carries the full burden. It clarifies that "status" is an option set by name, but owner, number, and itemId are entirely undocumented and their meaning must be inferred from the name alone.

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 gives a specific verb and resource: it "sets one item's exact Status option by name," and labels itself a compatibility alias for the semantic Status write path. This distinguishes it from the sibling field/priority writers, though it never names which tool it aliases, so the differentiation stays implicit.

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?

"Compatibility alias for the semantic Status write path" hints that a preferred alternative exists but does not say when to use this tool versus update_github_project_item_field, update_work_item_status, or its canonical counterpart. No prerequisites, no exclusions, no context beyond the alias framing.

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