lookup_warframe

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does describe what kinds of data are returned, which is useful, but it does not mention whether the operation is read-only, any potential side effects, rate limits, or error conditions. The description is adequate but not richly transparent.

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, well-organized sentence that front-loads the core action and resource, then lists the scope of information. There is no fluff or redundancy.

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 tool is a simple lookup with one parameter and no output schema. The description lists the categories of information returned, which is sufficient for basic understanding. However, it does not mention any limitations, such as how many names can be looked up at once (although the schema specifies maxItems=10) or what happens if a name is not found. Minor gaps prevent a 5.

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 for the single 'names' parameter is 100%, and the schema already provides a clear description with examples. The tool description adds the phrase 'by name,' which slightly reinforces parameter semantics, but this is already implied in the schema. Thus, the description adds minimal value beyond the schema.

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?

Description states a specific verb ('Look up') and resource ('Warframes by name'), and enumerates the exact kind of information returned (stats, abilities, component drop sources, build requirements, vault status). This clearly distinguishes it from sibling lookup tools for weapons, mods, and items.

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 usage context is clear: use this tool when you need information about Warframes. However, it does not explicitly mention when not to use it or point to alternatives (e.g., lookup_weapon for weapons), so it falls short of a perfect score but is above the 'no guidance' level.

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