set_project_item_archived

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is largely covered by structured data. The description adds value by noting reversibility and that the underlying Issue/PR is preserved—context beyond annotations. This is a reasonable addition, though it doesn't describe auth requirements, rate limits, or effect on other project data, which is acceptable for a simple toggle given annotation coverage.

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?

Single compact sentence, front-loaded with the core action. Efficient and lacks filler. It loses a point only because the brevity comes at the expense of parameter guidance and usage nuance, though the core message is well captured.

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 simple boolean toggle with no output schema, the description is near-sufficient, but with a 0% schema coverage and 6 parameters (5 required), some parameter semantics would elevate completeness. The reversibility and non-destructive notes partially cover the behavioral context. No guidance on which account/owner to pass for org vs. user projects is given, which could matter.

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 carries the entire parameter burden but adds no parameter-specific detail. The 'archived' boolean parameter is inferable from 'Archive or restore,' but the description doesn't clarify which value maps to which state, nor distinguish account/owner/projectId semantics. For 6 parameters with zero schema coverage, the description under-delivers on parameter clarification.

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?

Clear specific verb+resource: 'Archive or restore a GitHub Projects v2 item.' States scope (Projects v2) and explicitly notes it's reversible and does not touch the underlying Issue/PR, which distinguishes it from delete operations. The name and description align tightly.

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 conveys the operating context (GitHub Projects v2) implicitly via the name and the word 'Projects v2' in the description. However, it does not explicitly state when to use this vs. alternatives like delete_repository or clear_project_item_field. The reversibility note implies a when-to-consider distinction but no explicit exclusions or alternative tool references are given.

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