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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered structurally. The description adds value by disclosing the data payload (including booking policy and plan status) in the absence of an output schema, but says nothing about freshness, auth/permission requirements, or response shape.

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?

A single compact sentence with zero filler, front-loading the highest-value information (whose profile and what fields). It is a bare noun phrase without a verb, which slightly reduces clarity but wastes nothing.

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 tool with rich annotations, this is close to sufficient: the field enumeration effectively stands in for the missing output schema. The only gap is the absence of any routing guidance relative to the closely related hours/settings/report tools.

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 the baseline of 4 applies. There is no parameter surface for the description to explain or for the agent to get wrong.

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 enumerates the concrete fields returned (name, address, contact, opening hours, booking policy, rating, plan status), so an agent knows exactly what data this tool surfaces. It lacks an explicit verb and does not distinguish itself from siblings like get_business_hours or get_settings, which appear to overlap on 'opening hours' and profile/settings data.

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?

There is no guidance on when to call this versus get_business_hours, get_settings, or get_report, all of which plausibly return overlapping business information. No prerequisites, no exclusions, and no stated context for use.

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