validate_gem_quality

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the categories of findings but never states that this is a read-only audit (no mutation of the build), what the output looks like, or how findings are ordered/prioritized. Listing what it 'identifies' gives some value, but the safety and result-shape profile of a validation tool is left blank.

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 main action front-loaded and no filler. The only looseness is the capitalised in-game term 'Exceptional', which is unexplained for a reader unfamiliar with the domain.

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 2-parameter, read-only-style audit with no annotations and no output schema, the definition covers what is checked but not what comes back or how to interpret it. An agent knows what to send but not what to expect, and no guidance is given on build_name scope (e.g. whether the build must exist or be the active one).

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 100%, so both parameters are already documented, including the default for 'include_corrupted'. The description implicitly links 'corruption targets' to that flag, but adds no syntax, format, or edge-case detail beyond the schema.

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 uses a specific verb and resource ('Check all gems for quality and level improvements') and enumerates exactly what it surfaces: missing quality, Exceptional upgrade opportunities, and corruption targets. It is clearly a gem-audit tool, but it does not distinguish itself from the sibling 'gem_upgrade_path' or 'validate_build', which plausibly overlap with 'upgrade opportunities'.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites are stated. The agent must infer from the one-line purpose whether to call this versus 'gem_upgrade_path' for upgrades or 'validate_build' for a broader build check.

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