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

Annotations already indicate this is a write operation (readOnlyHint=false) and not idempotent or destructive. The description adds some context by explaining the action types (block/open/remove) and that it applies to business or staff/room, but does not disclose side effects like impact on existing bookings, cancellations, or error scenarios. With annotations covering the basic safety profile, the description provides moderate additional transparency.

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?

The description is a compact three-sentence paragraph that front-loads the core purpose and key usage hints. Every sentence contributes value, and there is no unnecessary verbosity. However, it could be slightly better structured with explicit parameter explanations, but overall it is efficient.

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?

With 7 parameters, no output schema, and very low schema coverage, the description is insufficient for an agent to correctly call the tool in all cases. It does not explain how to specify the target (whole business vs staff/room), what 'reason' is used for, the semantics of overlapping blocks, or the effect on availability. The description covers the primary use case but leaves significant gaps.

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 only 14%, so the description must compensate for undocumented parameters. It explains 'to', 'from', 'open', and 'remove_exception_id' implicitly, but does not clarify 'resource_id' (which likely identifies staff/room), 'business_id' (only partially explained in schema), or 'reason' (purpose of the block). The description does not adequately help an agent understand the full set of 7 parameters.

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?

The description clearly states the tool's purpose: for business owners to block or open time for the whole business or a specific staff member/room, and to remove blocks. It uses specific verbs (close, open, remove) and identifies the resource scope, distinguishing it from other owner_* tools that manage schedules or bookings.

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?

The description explicitly restricts usage to business owners signed in to Awning and explains the main scenarios (closing for day off/break/holiday, opening extra time with open=true, and removing a block with remove_exception_id). However, it does not mention alternatives or when not to use this tool, such as setting regular schedule hours versus one-off exceptions, which could be inferred but is not explicit.

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