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

Discloses a lot beyond the annotations: transactional all-or-nothing semantics with per-row error reporting, the 100-item cap, the 'executes immediately' timing, the rule that identical units become one asset with a quantity, and the receptionist-notification side effect. None of that is derivable from the schema or the safety hints alone.

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?

Front-loaded with the core action and scope, then constraint, then semantics, then prerequisite – a logical order with no filler sentences. It is dense but every sentence carries information; a shorter variant would lose the atomicity and quantity rules.

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 write tool with an output schema, no return-value description is needed, and the description covers atomicity, error behavior, limits, side effects, and the prerequisite call. The annotations cover the safety profile (non-destructive, non-idempotent), leaving no critical gap for an agent before invoking.

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?

Adds real meaning the schema cannot: it explains every bookingType enum value (nightly, day, date_range, not_applicable) and clarifies the quantity modeling convention (identical units collapse into one asset with a quantity). It leaves hideName, checkInTime, checkOutTime, and description to the schema, so it is not fully covering.

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 verb and resource ('Adds bookable assets (rooms, campsites, vehicles, equipment) to the connected Nexwin account') plus scope limits (up to 100 per call) and a side effect (notifies the live receptionist). This is clearly distinguishable from siblings like list_assets, import_customers, and create_booking.

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?

Gives a concrete use case ('set up a whole list the user has pasted or uploaded') and a sequencing rule ('Call list_assets first to avoid clashing names'). It stops short of saying when not to use it or what to do about existing assets, so it is strong but not exhaustive.

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