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

The annotations already disclose that this is a non-readonly, idempotent mutation that is not destructive and operates in an open world. The description adds some useful context, namely that settings affect hotel search results and that updated settings are returned, but it does not add deep behavioral detail beyond that.

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 heavily formatted with many sections and repetitive bullet points for a tool that takes only one boolean parameter. While it is front-loaded with an Overview, the amount of redundant prose makes it far from concise.

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 one-parameter mutation tool with 100% schema coverage and annotations, the description is more than sufficient. It covers what the tool does, when to use it, and what it returns; the only minor gap is that it does not reference the sibling read tool.

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 schema fully documents the single parameter advancedAccessibility, including its boolean type and meaning. The description repeats this in the Quick Start section without adding syntax, format, or side-effect details beyond what the schema already provides.

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 configures supply customization preferences, specifically enabling or disabling advanced accessibility options for hotel searches. It uses a specific verb and resource, but it does not distinguish itself from the sibling read tool get_supply_customization.

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?

A 'When to Use' section exists, but its bullets largely restate the purpose rather than providing true when-to-use guidance. It doesn't name alternatives such as get_supply_customization or specify when not to use this tool.

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