list-walls

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

Despite no annotations, the description fully discloses that the tool is read-only and serves as an inspection step before modification. It also warns about the large number of walls in populated scenes and recommends the doorsOnly filter. No behavioral traits are omitted.

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 three sentences, each serving a distinct purpose: what the tool returns, guidance on filtering, and behavioral context. It is front-loaded with the most critical information (purpose and field list) and contains no redundant phrases.

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?

Given the tool's low complexity (2 parameters, no output schema, no annotations), the description provides sufficient context: return fields, filtering advice, read-only nature, and relation to sibling tools. An AI agent can confidently decide when and how to use this tool.

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 already provides full descriptions for both parameters (100% coverage). The description reinforces the doorsOnly parameter by contextualizing its use ('the usual edit loop'), but does not add new semantic information beyond what the schema provides. Baseline 3 is appropriate.

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 'List walls on a scene' and enumerates the fields returned (id, segment, channels, etc.). It distinguishes this from sibling tools like create-walls, update-walls, and delete-walls by positioning it as the 'inspect step before update-walls / delete-walls.' This provides a specific verb+resource combination with clear scope.

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 description explicitly guides usage: 'A populated scene carries HUNDREDS of walls: pass doorsOnly:true to get just the doors (the usual edit loop).' It also labels the tool as 'Read-only; the inspect step before update-walls / delete-walls,' clarifying when to use this tool versus its mutating siblings.

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