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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description adds context rather than carrying the safety profile: it discloses the fields returned, the meaning of the demo:true flag (a sample listing that is not a real place), and that offering_id values originate here. It does not cover error behavior for invalid identifiers, but the extra disclosure is substantial.

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?

Dense but front-loaded: the content list leads, followed by the demo flag, usage routing, dependency note, and exclusion. Every sentence earns its place, though the content enumeration is a long clause that borders on packing too much into one sentence.

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?

No output schema exists, so the description must explain returns, and it does: it enumerates the full card contents and explains the demo flag. Combined with the usage routing and offering_id provenance, an agent has everything needed to call it correctly.

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 (business_id UUID or slug, page address format). The description adds only the example page address and reinforces the offering_id relationship, so baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Full card of one business') and enumerates exactly what the card contains (offerings, prices, extras, booking rules, intake questions, hours, cancellation policy, contacts). It explicitly contrasts with sibling get_availability ('Not for free times'), so the agent can distinguish it without opening any schema.

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?

States the two entry conditions explicitly: 'Use it after search_businesses, or when you already have a business_id, a slug or an Awning page address'. It also names the alternative for availability and explains the downstream dependency ('The offering_id values the booking tools need come from here').

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