update_ceiling_floor_vent

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

Describes partial update (only provided params changed), returns confirmation string. No annotations to contradict. Lacks auth/rate limit info but sufficient for a simple update tool.

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?

Well-organized with intro, parameter list, returns. Each sentence is informative and concise. No fluff.

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?

Covers behavior, all 8 parameters, and return value. No gaps given complexity. Output schema existing but description still explains return type.

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?

Detailed parameter descriptions with constraints (e.g., for connection: need both comp_top and comp_bottom), types, units, and default behavior (None leaves unchanged). Compensates for 0% schema coverage.

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?

Clear statement: 'Update an existing ceiling/floor vent.' Differentiates from add_ceiling_floor_vent sibling. Specific verb and resource, with explanation of selective update.

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?

Explicitly says to select by vent_id and only changed parameters are updated. Implies use when modifying existing vent, not adding. No explicit alternatives but context is clear among siblings.

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