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

Annotations only declare readOnly/openWorld=false/destructive=false; the description adds materially more: it is free, offerings are paginated 60-per-page cheapest-first with `offerings_page` and a next offset, and `live_data` (platform, synced_at) signals a connected shelf where offerings carry `source: connector`, variants with `inventory` (null = unknown), and `connected`-method actions route through place_order/book_slot. It also warns that nothing is sent, booked, ordered or paid without the user's 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?

The synonym caveat and the 'Free. One business in full' payload statement are front-loaded, which is the right ordering. The middle block is a dense wall of parenthetical field descriptions that takes effort to parse, and some of it could be itemized, but nearly every clause carries return-shape information justified by the absence of an output schema.

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 carries the full burden of explaining the return value — and it does: identity fields, paginated offerings, the six actions with links and `required_fields`, delivery/pickup/on_site/at_customer with area, fee and deadline, freshness, and the connector variant. For a one-parameter read tool this is complete.

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% for the single required parameter and the schema already says 'the business id from search_catalog'; the description adds no further meaning about the id's source or format beyond that. With one fully documented parameter, the baseline 3 is correct even though the response-field detail (`offerings_page`, `live_data`) is handled elsewhere in the text.

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 with the specific verb+resource relationship: it is a SYNONYM of get_card, then states it returns 'One business in full, in the same shape for every trade.' An agent immediately knows both what it returns and that a functionally identical sibling exists, so no schema inspection is needed to disambiguate.

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 explicit trigger phrases («can they deliver to me», «are they open now», «what else do they do») and a fallback condition: when search_catalog offered a business with nothing listed and the next step is a telephone call. It also names the sibling alternatives (get_card for the name you know, place_order/book_slot for the connected-method actions) and states the read/quote/order separation rule, so when-not-to-act is covered too.

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