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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description's added value is provenance and scoping: 'Each block names its source and the date it was read' and the rules are account-specific including the seller's own house rules. It does not discuss caching or rate limits, but adds genuine behavioral context beyond 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?

Front-loaded with the core purpose, followed by a dense but purposeful enumeration of what is returned and a short operational instruction at the end. The single long sentence is information-heavy rather than padded, though the list could be broken up for readability.

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?

An output schema exists, so return structure need not be described, and the description already clarifies the account-scoped nature, the source/date provenance of each block, and the correct workflow order. An agent has everything needed to decide and call correctly with a single optional parameter.

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 with 100% schema description coverage, which already explains it comes from list_accounts and is optional for single-account setups. The description only implies account-specificity ('on this account') without adding format or fallback detail beyond the schema, so the baseline 3 applies.

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 names a specific verb (read) and resource (the marketplace's own listing rules for a product listing on this account), then enumerates the exact content blocks returned: title structure/length, forbidden words, HTML rules, picture limits, mandatory attributes, EAN/brand rules, mattress notes, rejection reasons, and house rules. It is clearly distinguishable from siblings like listing_check and offers_validation_errors, which validate rather than inform.

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?

Explicit sequencing: 'read before writing any title, description, pictures or attributes' and 'Do not guess a format: call this, then write, then listing_check.' This states when to use it, why (avoid guessing), and names the follow-up sibling tool, leaving nothing to inference.

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