Retrieve floor plans for swarm worlds, including size, walls, doors, and ASCII layouts, to choose or set up simulation environments.
Floor plans for the swarm worlds (use as layout: plan:): size, walls, doors and the ASCII text.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the return payload shape (size, walls, doors, ASCII), which implies a safe read, but never explicitly states read-only behavior, permissions, or output format/pagination.
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 compact sentence that front-loads the resource and then the payload. Dense and waste-free, though the parenthetical is slightly awkwardly embedded mid-sentence.
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 zero-parameter list tool with no output schema, the description adequately covers what the tool returns and how the results are referenced. It could say more about whether all plans are always returned, but nothing essential to invoking it is missing.
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 schema declares zero parameters, so per the rubric the baseline is 4. There is nothing for the description to compensate for.
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?
States a specific resource (floor plans for the swarm worlds) and enumerates the returned content (size, walls, doors, ASCII text). The 'list' verb is implied by the name and the plural resource. It distinguishes from save_plan but not explicitly from catalogue or other list_* siblings.
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 parenthetical 'use as layout: plan:<name>' hints at how the returned names are consumed, which is genuine usage context. However, it never says when to call this versus save_plan or catalogue, so selection guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.