assets-get-available-tilemaps

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

No annotations are provided, so the description carries the burden. It explains the tool returns a list of tilemap keys and gives context about Tiled tilemaps, but does not disclose error behavior or side effects. It is adequate for a read-only query but lacks depth.

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 four sentences long, front-loaded with the main action, and provides necessary context without excessive detail. It is efficient but could be slightly trimmed.

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 complete for a simple list-retrieval tool with no parameters and no output schema. It explains tilemap origin and key usage, making it contextually sufficient. Minor gaps exist in clarifying relationship to sibling tools.

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 input schema has zero parameters with 100% coverage, so the description has no parameter details to add. Baseline of 3 applies as schema alone is sufficient.

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 searches for available Tiled tilemap files in asset packs and returns tilemap keys. The verb 'Search' and resource 'asset packs' are specific, and the tool name with 'tilemaps' distinguishes it from siblings for other asset 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?

Usage is implied from the name and description: it is used to get tilemap keys. However, no explicit guidance is given on when to use this tool versus alternatives like assets-get-available-textures or scene-add-editable-tilemap, leaving room for ambiguity.

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