list_warframes

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds that results include stats, polarities and abilities, which is useful, but says nothing about how the 'limit' parameter affects the response or whether results are partial matches.

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?

A single dense sentence that front-loads the verb, the resource scope and the returned data. No filler, no repetition of the tool name.

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 read-only search tool with no output schema, the description does the essential work of stating what fields come back (stats, polarities, abilities). The only gap is how 'limit' and the 'kind' default behave, which an agent may need to call it correctly.

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 67%: 'query' is documented as 'Part of a name' and 'kind' has an enum, while 'limit' has no description anywhere. The description's 'by name' reinforces the query semantics (substring matching) but adds nothing for limit or kind defaults.

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 names a specific verb ('Find') and enumerates the exact resource set (Warframes, companions, Archwings, Necramechs) plus what data comes back (stats, polarities, abilities). This clearly separates it from siblings like list_weapons or search_mods, though no sibling is named explicitly.

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 phrase 'by name' implies a lookup use case, but there is no explicit when-to-use or when-not guidance, and no pointer to alternatives such as warframe_build or suggest_warframe_build when the agent actually wants build data. Usage is only implied.

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