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

Adds substantial context beyond the annotations: transactional atomicity ('a bad entry changes nothing'), upsert-by-name semantics with reactivation of inactive items, the rule that omitted items are untouched so the call is safe to repeat, and the scope requirement locations:write (Admin role). It also describes the return payload (full setup plus bookingPage.problems checklist), which the annotations cannot convey.

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 prerequisites, then alternatives, then return and auth — a sensible ordering. Some sentences are slightly redundant with structured data ('repeating the call is safe' overlaps idempotentHint=true), keeping it just short of maximally tight.

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 5-parameter nested-object tool with no output schema, the description covers prerequisite, alternatives, atomicity, merge semantics, authorization scope, and the shape of the return value. Nothing material an agent needs in order to call it correctly 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?

Schema description coverage is 100%, so the baseline is 3; the description still adds real value the schema does not state, namely that types and doors are matched by name, that existing names are updated and reactivated, and that doors reference types by name so ids are unnecessary. It does not detail the settings or weekly-hours parameters, but those are already well documented in-schema.

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 ('Configure an existing location') and enumerates exactly what the single call bundles: scheduling settings, weekly hours, appointment types, and doors. It explicitly separates itself from create_location and from the focused update tools, so an agent can identify it without opening a schema.

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 explicit routing rules in both directions: 'Prefer it for first-time setup or several changes at once; for a single change the focused tools are simpler: update_location_settings, set_weekly_hours, create_/update_appointment_type, create_/update_door.' It also states the prerequisite ('doesn't create the location itself (use create_location first)') and the required scope/role.

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