get_equipment

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

No annotations provided; description mentions the underlying mechanism (RuneLite HTTP Server plugin) but lacks disclosure of side effects, permissions, rate limits, or requirements like plugin running.

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?

Two sentences, no extraneous information, front-loaded with core action and resource, ends with key differentiator.

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, parameterless retrieval tool with no output schema, the description adequately covers the source and reliability. Sibling tools like get_inventory provide context, but no missing critical information.

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?

Tool has zero parameters and 100% schema coverage; description adds no parameter info needed, but succinctly covers the tool's purpose. Baseline 4 for parameterless tools.

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?

Clearly states verb 'Get' and resource 'currently equipped items'. Distinguishes from vision-based alternatives by mentioning RuneLite HTTP Server plugin and reliability.

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?

Implies usage context by stating reliability advantage over vision, but does not explicitly specify when to use or exclude alternatives, nor provide when-not-to-use criteria.

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