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

Beyond the readOnly/openWorld annotations it discloses that calls are free, that returns are capped at 60 offerings sorted cheapest first, what live_data/synced_at mean, that connector-sourced offerings carry inventory (null = unknown), and that connected-method actions route to place_order/book_slot. It also states the safety posture: nothing is sent, booked, ordered or paid without user permission.

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?

Front-loaded with the disambiguating synonym note, then grouped cleanly by returned sections (identity, offerings, actions, fulfillment, freshness, live_data). It is long, but with no output schema most of the return-shape detail earns its place; the closing pointer to server instructions is slightly generic boilerplate.

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 carry return-value semantics — and it does, enumerating every response section, the 60-offering cap and ordering, fulfillment modes with fee/deadline, and freshness fields. For a single-param read tool this leaves nothing an agent needs 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?

There is a single parameter with 100% schema description coverage ('the business id from search_catalog'), so the schema already carries the semantics. The description adds no format, validation or sourcing detail about `id` beyond what the schema states; baseline 3 applies since the schema 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?

The description opens by declaring the tool a synonym of get_card and then states a specific verb+resource: fetch one business 'in full' with a fixed shape (identity, offerings, actions, fulfillment, freshness). An agent can immediately tell it apart from search_catalog, list_cards, get_offering and get_card itself.

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?

It gives three concrete user-question triggers ('can they deliver to me', 'are they open now', 'what else do they do') plus an explicit fallback scenario where search_catalog returned a business with nothing listed and the next step is a phone call. The synonym framing also removes the need to choose against get_card, so no exclusion clause is missing.

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