skills.reviewReject

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

No annotations are provided, so the description carries the full behavioral burden. It says 'reject' without disclosing whether the rejection is reversible, what state transition it triggers, whether it requires an in-review status, or what permissions are needed — significant gaps for a mutation tool with zero 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?

A single short sentence with no waste and the action front-loaded. However, it is under-specified rather than genuinely concise — the brevity comes at the cost of the behavioral and parameter detail 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?

A mutation tool with no annotations, no output schema, and 0% parameter description coverage should compensate with more context. Missing path format, side effects, state prerequisites, and the outcome of a successful rejection leave the definition incomplete.

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% and the description explains only 'notes' (as reviewer notes). The required 'path' parameter is never clarified (file path vs. skill identifier vs. registry path), and 'reviewed_by' is not mentioned at all.

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 (Reject) and resource (a skill), and the sibling family (skills.reviewApprove, skills.reviewRequest, skills.reviewStatus) makes the action immediately legible as part of the review workflow. It does not explicitly name the approve sibling it is the inverse of, but the verb 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 when-to-use guidance, no exclusions, and no reference to alternatives such as skills.reviewApprove or skills.reviewRequest. The reviewer context is only inferable from the sibling names, not from the description.

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