Lists save-defined items and shop templates, including IDs, names, icons, currency values, and each template's buy/sell goods and prices.
List the items defined in a save (id, name, icon, value in a currency) and its shop templates (what each sells and buys, at what price).
| Name | Required | Description | Default |
|---|---|---|---|
| mapPath | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds scope (items AND embedded shop templates, with pricing) but says nothing about what 'a save' means, whether a missing mapPath yields defaults, or how large the result can get.
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 and resource and spends its remaining words on return contents rather than filler.
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?
With no output schema, the description responsibly enumerates the payload (id, name, icon, currency value, shop buy/sell prices). The remaining gap is the sole parameter's semantics and the behavior with an absent/incorrect mapPath.
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?
There is one parameter (mapPath) at 0% schema coverage, and the description never mentions it. 'The items defined in a save' loosely hints that a path selects the target save, but it does not clarify whether mapPath is required, what form it takes, or what happens when omitted.
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?
Specific verb 'List' with a well-scoped resource: items defined in a save, plus their shop templates. It also enumerates the returned fields (id, name, icon, value, buy/sell prices), which makes it distinguishable from mutators like scene_add_item and scene_add_shop, though it doesn't name a sibling 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?
Usage is only implied: an agent can infer this is the inspection step before scene_add_item/scene_add_shop, but the description states no when-to-use condition, no prerequisites (e.g. must a save exist?), and names no alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.