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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds the key reassurance that 'existing bookings stay' — clarifying what the destructive hint does not touch. It does not explain whether pausing is reversible beyond toggling, nor what happens to availability visibility while paused, so it stops short of full disclosure.

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 short sentences: eligibility first, effect second, routing third. Every clause carries information and nothing is padded.

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 two-parameter toggle with full schema coverage and no output schema, the description covers scope, effect on existing bookings, and the alternative tool. Minor gaps remain around what a pause changes for customers viewing the business, but nothing an agent needs in order to invoke 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 coverage is 100%, so both parameters are already documented, including the paused boolean semantics that the description restates. The description adds no business_id guidance of its own; 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?

States a specific verb pair (stop taking / resume) and the resource (new bookings), plus the scope restriction to business owners signed in to Awning. The sibling owner_block_time is named with the exact condition that separates the two.

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 an eligibility gate ('only for business owners signed in to Awning'), a duration-based rule of thumb ('break of days or weeks'), and an explicit redirect to owner_block_time for a single day or a few hours. No inference required.

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