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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description's job is content disclosure — which it does well by listing the returned payload categories and how booking/payment modes work at that business. It stops short of covering failure behavior (invalid slug, unknown business) or any rate/limit constraints.

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 sentences, front-loaded with the resource identity before the payload enumeration, and every clause maps to real returned data. The trailing parenthetical on booking confirmation and payment methods is the densest part but still informative rather than filler.

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?

A single-parameter read tool with no output schema and full annotation coverage: the description compensates by enumerating the return payload and the booking mechanics, which is precisely the missing piece. An agent can decide and call correctly from this.

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% and the single parameter is fully documented there; the description repeats the same 'slug or lokuli.com/shop/... link' phrasing without adding format examples or normalization rules. Baseline 3 is appropriate when the schema already does the work.

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?

Specific verb+resource: 'details of one business on Lokuli', followed by an enumeration of exactly what is retrieved (services/prices/hours/team/address/reviews/booking flow). The 'one business' framing implicitly contrasts with the search-style siblings, but no sibling is named, so the differentiation is only inferable.

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 implies the usage context (look up a single business when you have its slug or shop link) and gives input guidance, but it never states when to use this versus find_businesses or get_available_times, and offers no exclusions or prerequisites.

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