Disenchant loot shards for essence

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the mutation risk is partially covered. The description adds real value beyond them: it states inventory items are consumed, that the action cannot be undone, and the write-allowlist requirement for POST /lol-loot/v1/recipes/*/craft. It stops short of describing failure modes or per-call limits, but the irreversibility and permission context are well disclosed.

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?

Front-loaded with what the tool does, then usage routing, then a clearly labeled Behavior: line. Every sentence carries distinct information with no repetition of the schema.

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 two-parameter mutation with no output schema, the definition covers purpose, routing, irreversibility, and permission requirements. The only mild gap is how the call reports success/result counts, but the essence outcome is stated, so an agent has what it needs to invoke correctly.

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 lootId and count are already fully documented in the schema, including the example format. The description only restates 'by lootId' and adds nothing about count semantics or batching behavior, so baseline 3 applies.

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?

Specific verb (Disenchants) + resource (champion or skin shards) + keying parameter (by lootId) + outcome (Blue or Orange Essence). Nothing in the sibling list does the same thing, and the scope 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?

Explicit when-to-use ('convert unwanted or duplicate shards into crafting essence') and an explicit alternative with a condition: use lol_analytics_loot_summary first to preview potential yields. That is a genuine routing rule, not just implied context.

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