Get character inventory

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

Annotations already mark the tool as read-only and open-world, so the description's added value is the fallback behavior: it first tries the GGG API and falls back to poe.ninja or an active PoB build. This is useful context that tells the agent data may come from different sources with potentially different freshness or fidelity.

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?

A single, front-loaded sentence that names the action, the target data, and the source strategy with no filler. Every phrase earns its place.

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 simple read-only fetch with one optional parameter and no output schema, the description adequately conveys what is returned (equipped items and skills) and how data is sourced. It stops short of describing the response structure or error behavior, but the high-level content is clear enough for an agent to call it 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?

The schema fully documents the only parameter with 100% coverage, including the 'optional if active build is loaded' condition. The description reinforces this by mentioning the active PoB build fallback, but it does not add new parameter details beyond what the schema already provides.

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?

States a specific verb and resource: 'Fetch a character's equipped items and skills.' It also names the data sources (GGG API, poe.ninja, active PoB build), which clearly differentiates it from sibling tools focused on passive tree, defenses, or offense stats.

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?

Usage context is implied by the resource name and by the note that characterName is optional if an active build is loaded. However, it does not explicitly state when to prefer this tool over siblings like get_defenses, get_offense_stats, or get_character_state, nor does it give exclusion criteria.

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