parse_item

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

Discloses affix detection is best-effort and unmatched lines are returned under 'unrecognized'. Tiers and ranges are corpus facts. No annotations exist, so description carries full burden; it does well but could mention potential side effects or data sources.

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?

Concise 4-5 sentences, front-loaded with purpose. Structure is clear but could be slightly tighter without losing information.

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?

Given output schema exists, description sufficiently covers what is returned (affix tiers, open slots, unrecognized lines). Complete for evaluating drops and planning crafts.

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?

Only one parameter 'text' with 0% schema coverage; description explains it expects in-game clipboard or PoB item text, adding meaning beyond schema. Could specify expected format or constraints.

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?

Description clearly states it parses PoE2 item text and enriches it with mod tiers and open slots. It distinguishes from sibling 'equip_item' by directing to that tool for build impact, making purpose distinct and specific.

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 says to use it to evaluate a drop or plan a craft, and to use 'equip_item' to see build changes. Provides clear context but could be more explicit about when not to use it.

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