horizon_torn_getMyInventory

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

No annotations are provided, and the description lacks any behavioral details (e.g., authentication requirements, caching, rate limits, or what data is returned). The agent has no information about side effects or constraints.

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?

The description is extremely concise (one sentence). While it is front-loaded, it may be too terse: it lacks necessary detail about scope and usage, making it minimally adequate.

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 no output schema, no annotations, and many sibling tools (e.g., getMyAmmo, getMyEquipment), the description is severely incomplete. It does not specify what 'inventory' includes, how to filter, or how to handle pagination, leaving the agent without sufficient context for correct invocation.

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 schema description coverage at 67%, the description adds no additional meaning to parameters. For example, it does not clarify that 'cat' filters inventory category or that 'limit' and 'offset' control pagination. The description does not compensate for the schema's lack of documentation on two parameters.

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 'Get your inventory' clearly states the tool's action (get) and resource (inventory). However, it does not differentiate from sibling tools like 'horizon_torn_getMyAmmo' or 'horizon_torn_getMyEquipment', which also retrieve specific inventory subsets.

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?

No usage guidance is provided. The description does not explain when to use this tool over alternatives such as 'getMyAmmo' or 'getMyEquipment', nor does it mention any prerequisites or context.

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