lookup_item

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

With no annotations, the description must fully disclose behavior. It mentions 'dynamic formatting' but does not explain what that entails, data source, error handling, or whether the lookup is case-sensitive or fuzzy. Key behavioral traits are missing.

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?

One sentence that is front-loaded and efficient. It could be slightly more structured (e.g., separating purpose from behavior), but it is concise.

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?

The description is insufficient given no output schema or annotations. It does not specify return format, error messages, or behavior when items are not found. The number of results is implied by schema maxItems, but not stated.

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% for the single 'names' parameter, with examples in the schema description. The description adds 'dynamic formatting' but does not clarify parameter semantics further. Baseline 3 applies.

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 clearly states the tool looks up items by name, listing examples like arcanes, resources, and blueprints. It distinguishes from siblings like lookup_warframe or lookup_mod which target specific types.

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?

The description implies this is for generic item lookups, but does not explicitly state when to use it versus siblings like lookup_weapon or lookup_mod. No when-not or alternative guidance provided.

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