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

Annotations already indicate this is not read-only, is idempotent, and is not destructive. The description adds useful behavioral context beyond that: 'Existing bookings stay' and the pause is temporary, which clarifies the tool's effect on existing reservations.

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?

Two short sentences deliver the key information with no filler. The restriction, behavior, and parameter meaning are all front-loaded and easy to parse.

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 simple two-parameter boolean/set operation, the description covers the essential context: who can use it, what it does, how the parameter changes behavior, and that existing bookings are unaffected. No output schema is present, so return-value details are not required.

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?

The description explains the meaning of the 'paused' parameter values (true stops new bookings, false resumes them), compensating for the schema's lack of a description on that parameter. 'business_id' is adequately covered by its schema description, so both parameters are semantically clear when combining schema and description.

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?

Description states a specific action: temporarily stop taking new bookings or resume them, tied to the 'paused' boolean. It clearly identifies the tool's resource and differentiates it from cancellation by noting that existing bookings remain.

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 gives clear context by restricting use to business owners signed in to Awning, and explains the two states of use (paused=true vs paused=false). It does not explicitly name alternatives, but the scope and conditions are unambiguous enough for an agent to know when to invoke it.

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