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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: rule sets are shared across products like a tax table, and editing one cascades to every dependent product. It does not describe return shape or pagination, keeping it at a 4.

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 sentences, front-loaded with the purpose and fields, then the usage directive, then the sharing warning. The tax-table analogy and the editing caveat slightly overlap the sharing concept, but every sentence carries actionable information.

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 zero-parameter, read-only list tool with annotations covering safety and no output schema, the description is nearly sufficient: it explains what a rule set holds and the cross-product sharing semantics. A brief note on what identifiers a returned set carries would fully close the loop.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. No contradicting or redundant parameter text is present.

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 (List) and resource (reusable booking policies/rule sets) and enumerates the fields contained (opening hours, slot length, buffer, lead time). It explicitly distinguishes itself from the sibling hub_create_booking_rules by framing itself as the prerequisite read step.

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 unambiguous when-to-use directive: 'ALWAYS read this before creating one and offer an existing set when it fits.' This names the alternative action (creating) and the condition (an existing set fits), 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.