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

Adds significant context beyond annotations: returns { removed: true }, unknown id yields not_found, and requires scope locations:write with Admin role. The description clarifies the idempotent semantics of reopening an already-open date and the authorization requirement.

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?

Three tight sentences front-loading the action, followed by id source, return shape, and auth requirement in priority order. No 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?

Complete for a 2-param mutation with annotations and no output schema. The description covers the reversal semantics, return value, error case, and required scope, leaving no gap for an agent to call correctly.

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 coverage is 100%, so both locationId and closureId are documented in the schema with clear provenance descriptions. The description's mention of 'a closure id from get_location_setup's upcomingClosures' reinforces but does not extend what the schema provides, so baseline 3 applies.

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?

Specific verb (Reopen) + resource (closed date) with explicit scope (one date added by add_closed_dates) and names the sibling tool it depends on. Clearly distinguishable from siblings like add_closed_dates and set_weekly_hours.

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 states the single-date granularity and the source of the id (get_location_setup's upcomingClosures). Names the prerequisite tool chain (add_closed_dates creates, get_location_setup provides the id), leaving nothing to inference.

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