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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: hard result caps (200 catalog records per type, 500 supplier options), an additional 'current crm:read authority' requirement for supplierOptions, and the explicit assurance that 'Existing operations and customer orders are not mutated by reading'. The only gap is that pagination/truncation behavior for hitting those caps isn't spelled out.

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 purpose is front-loaded in the first sentence, which is good. But the remainder is a dense run-on string of clauses packing response-field documentation (supplierOptions, commerceModel, expectedRevision, publication pointers) into prose, making it harder to scan than a short list would be. Every sentence carries information, but the packing hurts usability.

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 must carry the return-value burden, and it does: it names the returned blocks (supplierOptions with tenant-related suppliers and assignedPlaceIds, commerceModel with business fields/brands/versions/publication pointers) and the limits on how much comes back. What's missing is any note on how truncated results are signaled when a catalog exceeds the 200/500 caps.

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 and the schema is an empty object, so there is no parameter meaning to add. Baseline for a parameterless tool is 4; nothing in the description misrepresents the input contract.

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 uses concrete verbs and resources: it reads 'central locations, service areas and products/services' for the active tenant, plus archived entries and expectedRevision. That is far more specific than the title ('Standorte und Angebote lesen') and lets an agent recognize the catalog resource. It loses a point because it never distinguishes itself from the sibling get_business_model, and in fact mentions 'commerceModel contains tenant business fields', which blurs the boundary between the two tools.

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 implied workflow guidance: 'Copy newPlaceId/newOfferKey for creation' points the agent toward prepare_business_catalog_change, and 'larger catalogs require settings UI' tells it when this tool is insufficient. However, it never explicitly names an alternative tool or says when NOT to use this read, and the crm:read prerequisite is buried mid-sentence. The guidance exists but has to be inferred.

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