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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, but the description adds substantial context beyond them: the freshness/`synced_at` model, what `live_data` means when a shelf is the business's own connector, that `source: connector` offerings carry per-variant `inventory` with null meaning unknown, and that `connected` methods are executed via place_order / book_slot rather than here. It also confirms the safety contract (nothing is sent, booked, ordered or paid without the user's permission), consistent with the annotations.

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 framing and the use-case triggers are front-loaded well, but the body is a dense, run-on enumeration of return fields that includes an orphaned fragment ("`transparency`: the SuVerse Transparency rating ...") that reads like leaked schema documentation rather than prose. Most of the content is useful given the absence of an output schema, but the structure is strained and the sentences are overpacked.

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?

With no output schema, the description carries the full burden of explaining returns, and it does so thoroughly: identity fields, paged offerings, the six actions with `required_fields`, fulfillment modes with area/fee/deadline, and per-section freshness. For a single-id read-only tool this covers everything an agent needs to call it and interpret the result.

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?

Only one parameter exists and schema description coverage is 100% ("the business id from search_catalog"), so the schema already does the work and the description adds nothing about the id's format or provenance beyond the schema. The mentions of `offerings_page` and "the next offset" refer to response fields that are not input parameters, so they add no parameter meaning and slightly blur what is actually passed in.

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 by naming the resource and its scope ("One business in full") and immediately positions itself against a sibling ("SYNONYM of get_card, kept for agents that already know this name"). An agent can tell exactly what it retrieves and why it might pick this over get_card without opening either 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?

Gives concrete trigger queries ("can they deliver to me", "are they open now", "what else do they do") and a fallback scenario where search_catalog returned a business with nothing listed. It also defers to the server's HOW TO USE instructions and restates the separation-of-concerns rule. There is no explicit "do not use this, use X instead" exclusion beyond the synonym framing, which keeps it from a 5.

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