render_floor_plan

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

With no annotations, the description carries the full behavioral burden. It discloses what is rendered, that it returns one SVG per floor, and points to server instructions for conventions and the coherence contract. It does not mention side effects of the optional outputPath, but the schema covers that parameter.

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?

Two sentences, front-loaded with the core action and output. Every clause earns its place, and the pointer to server instructions is compact rather than duplicating conventions.

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 tool is complex with a deep nested spec and no output schema. The description states 'Returns one SVG per floor' but not the container format (e.g., array, object keyed by floor id) or how outputPath affects the result. It leans on external 'server instructions' for important contract details, leaving a moderate gap for an agent invoking it cold.

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no new parameter-level meaning beyond the phrase 'from a FloorPlanSpec', which is a slight reinforcement but not necessary.

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 states a specific verb ('Renders'), a resource ('interior floor plan'), and a source ('from a FloorPlanSpec'), plus the return form ('one SVG per floor'). The word 'interior' distinguishes it from the sibling render_site_plan without needing to open that tool.

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 implies usage: use when you need an interior floor plan from a FloorPlanSpec. However, it never explicitly says when not to use it or contrasts it with render_site_plan. No exclusions or alternatives are mentioned.

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