horizon_torn_getMyEquipment

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It does not state that this is a read-only operation, nor does it mention any auth requirements, rate limits, or side effects. The minimal text adds no transparency beyond what the name implies.

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 a single, efficient sentence with no wasted words. It is front-loaded and 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?

Given the tool's simplicity (no output schema, optional parameters), the description is marginally adequate. However, it lacks clarity on what exactly is returned (e.g., full item details or just names) and does not address how this relates to other inventory tools. Completeness is average.

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 coverage is 100% – all three parameters (key, comment, timestamp) are described in the schema. The description adds no new meaning or usage hints for these parameters. Baseline score of 3 is appropriate since schema handles parameter documentation fully.

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 states 'Get your equipment & clothing', which clearly identifies the verb (get) and resource (the user's equipment and clothing). It distinguishes from sibling tools like getMyAmmo, getMyInventory, etc., which target different specific data.

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 guidance is provided on when to use this tool versus alternatives such as getMyInventory or getMyWeaponExp. The description does not indicate prerequisites, exclusions, or contexts where this tool is preferred. The agent receives no decision support.

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