get_cosmetic

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

The description implies a read-only fetch operation, but without annotations, it does not explicitly state the lack of side effects, authentication requirements, rate limits, or what happens if the cosmetic item does not exist. The term 'fetch' suggests safety, but it's not confirmed.

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 sentence of 10 words with no fluff. It conveys the core action and output. However, it is too brief and could be expanded to include essential context without sacrificing conciseness.

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?

Despite low complexity (1 param) and an output schema existing, the description fails to provide critical context: it does not explain what 'infobox params' are, how to specify the item name, or any behavioral details. The 0% schema coverage makes this a major gap.

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?

The only parameter 'name' has no description in the schema (0% coverage), and the tool description does not explain what 'name' refers to (e.g., in-game item name, page title, identifier). No examples, constraints, or format hints are provided, leaving the agent to guess.

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 action ('Fetch'), the resource ('cosmetic item page'), and the output ('infobox params'). It distinguishes from sibling tools like get_page by specifying a specific item type. However, it could be more precise about what 'infobox params' entails.

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 like get_page, get_page_summary, or search_wiki. The agent is left to infer that it's for cosmetic items only, but there is no explicit when-to-use or when-not-to-use advice.

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