Get business hours

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

Annotations already declare readOnly, idempotent and non-destructive, so the description is free to add semantics: an empty list means closed, and the payload covers address, note, time zone and booking windows. The only omission is any hint of return shape or pagination, which matters little for a single-object read.

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 tight sentences with the payload front-loaded in the first line and the data-source clarification second. Nothing is padded, though the second sentence runs a bit long by stacking note, time zone, address and booking windows.

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?

There is no output schema, so the description has to carry the return values, and it does: hours per day, closed-day sentinel, note, time zone, address and booking lead times. A 4 rather than 5 because it does not say whether hours are staff-specific or business-wide only.

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 no parameters, so the baseline is 4. The description correctly explains that the result is implicitly scoped to the caller's business rather than requiring an id, which is the one parameter question an agent could have.

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 the resource and exactly what it returns: weekly opening hours, time zone, booking lead times, the note and address. This clearly separates it from get_business_profile and get_settings, which an agent might otherwise confuse with it.

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 framing 'Reads the opening hours set in Business details' implies this is the canonical source for operating hours, but it never says when to pick this over get_business_profile or get_settings, nor that it takes no arguments because it is tenant-scoped. Usage is inferable but not stated.

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