add_skill_group

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

No annotations provided, but the description fully covers behavior: group added enabled, effect reflected in stats, main skill preserved, spirit reservation impact, and the pitfall of inflating FullDPS with in_full_dps. Exceptionally thorough.

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?

Somewhat verbose but every sentence is informative. The description is front-loaded with the core purpose, then flows into format, behavior, and parameter guidance. Could be tighter but not wasteful.

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?

Covers purpose, behavior, format, parameter semantics, and usage guidance. Lacks mention of prerequisites (e.g., build must be loaded) or error handling. Still very complete given the tool's complexity and presence of output schema.

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?

With 0% schema coverage, the description explains both parameters: skill (paste format, newline support) and in_full_dps (boolean, with clear guidance on when to use True/False). Adds significant meaning beyond 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 clearly states it adds an ENABLED secondary skill group without changing the main skill, listing specific types (aura, herald, persistent buff). This distinguishes it clearly from sibling tools like set_skill.

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?

Explicitly describes when to use: for auras/heralds/buffs, and when to set in_full_dps=True (only for a second damage skill). Also references paste format from set_skill and advises checking spirit reservation with get_build_stats.

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