list_innerspace_floor_plans

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

With no annotations, the description carries the disclosure burden. It says responses are 'Returned verbatim,' and enumerates the exact fields per floor plan, including semantic details like ppm as the coordinate/height scale and when site_id appears. It does not cover every possible behavior (e.g., auth, pagination), but for a list operation the essential behavior is well disclosed.

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 front-loaded with the purpose, then a compact list of return fields, then parameter definitions. There is no filler; each line adds needed information.

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 having an output schema, the description adds the non-obvious context: asset paths require get_innerspace_asset, ppm is the coordinate scale, and site_id appears only when filtering. For a read-only listing tool with two parameters, nothing essential 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 provides only types and defaults with 0% description coverage, so the description must compensate. It does: host is defined as console name, ID, or composite ID (MAC:numericId format), and site_id is defined as an optional UniFi site filter matching product siteId. This fully clarifies both parameters.

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 opening sentence states the exact operation: 'List a console's InnerSpace floor plans,' with verb, resource, and scope. It also notes the Integration API and clarifies how image_url relates to get_innerspace_asset, distinguishing the tool from nearby list_innerspace_* 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?

It gives concrete context for calling: host can be console name, ID, or composite ID (MAC:numericId format), and site_id is optional with a clear filtering behavior. It points to get_innerspace_asset as the follow-up for fetching an asset path, which routes the agent appropriately, though it does not state explicit exclusions or alternatives.

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