pob_add_skill_group

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state, but the description never explains what is destroyed or replaced — the name says 'add', which suggests append-only while the annotations say destructive. Beyond the check_build pointer, it adds no context on limits (12 gems max), defaults, or failure behavior, so it does not close the gap the annotations open.

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 short sentences with zero waste; the mutation purpose is front-loaded and the validation requirement follows immediately.

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 destructive mutation tool with a nested array of four per-gem fields, no output schema, and no schema descriptions, the definition is thin. An agent still cannot tell what happens to existing skill groups, what the defaults for level/quality/enabled are, or how errors are surfaced.

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 compensate. It does clarify the single most important semantic — that 'id' values must be exact IDs from the gems catalog — but says nothing about level, quality, enabled, or label, nor about the 1–12 item bounds, leaving most of the nested object's fields undocumented.

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 states a specific verb and resource: adding a group of gems from exact catalog IDs. This distinguishes it from siblings such as pob_add_item (items) and pob_catalog (lookup). It stops short of naming what kind of group or which catalog is authoritative, leaving a little inference to the agent.

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?

It gives clear workflow guidance by naming pob_check_build as the required follow-up for compatibility and error validation, which is a genuinely useful routing instruction. It does not, however, say when to prefer this tool over other add tools or what prerequisites must hold before calling it.

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