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

Goes well past the annotations: it documents the default behavior (accepts every appointment type, inherits location hours), that the resource can exist before types are created, that limits are conditional on the location's door-assignment mode, that it returns the new door, and that it requires scope locations:write with the Admin role. The annotations only flag it as a non-idempotent, non-destructive write; the description supplies the operational context they lack.

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?

Dense but front-loaded with the verb and resource, and every sentence carries useful information (defaults, modes, alternatives, auth, return). The long middle sentence stacks several distinct constraints with parenthetical asides, which costs a little scanability but nothing is filler.

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?

No output schema exists, and the description compensates by stating it returns the new door. Combined with the defaults, mode caveats, alternatives, and required scope, an agent has everything needed to invoke this correctly and understand its side effects.

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 already 100%, so the baseline is 3. The description adds cross-cutting meaning beyond the field docs: omitting appointmentTypeIds means "every type, including types added later," and weeklyHours is "clipped to the location's," plus the note that both only matter in assignDoors mode. That elevates it slightly above baseline.

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 ("Add a dock door") and immediately distinguishes itself from siblings by naming update_door for editing and set_up_location for the combined type+door flow. An agent can tell exactly where this tool sits in the create/update family without opening any 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 when-to-use context (defaults mean it can be created before any appointment types exist) plus named alternatives and the condition selecting each (use update_door for limits, set_up_location to add types and doors together by name). It also states the mode-dependent caveat that limits only apply in assignDoors mode, not capacity mode.

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