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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds genuine behavioral context the annotations cannot: it enumerates returned fields (address, submission channel, account/money requirements, per-place rules, prior-attempt stopping point, manifest files) and discloses the `brief` variant framed for a browser-capable agent plus the owner-approval gating. It omits payload size, pagination, and whether reads are cached/fresh.

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 core purpose is front-loaded, which is good, but the body is a ~130-word run-on sentence packed with undefined internal jargon ('Marsell', 'listing kit', 'one text', 'manifest files'). Much of it is genuinely load-bearing return-value information, yet the structure makes it hard to scan and several terms are used before being explained.

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 correctly carries the burden of explaining what comes back, and it does so in detail, including the `brief` text artifact and the approval-gated sends. It falls short on scale/shape of the response (how many listings, how large `brief` is) and relies on unglossed product vocabulary that may not be meaningful to an outside agent.

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 description coverage is 100% and there is only one optional parameter (`project`), so the baseline is 3. The description never mentions `project` or the default-to-single-project behavior, adding nothing beyond the schema.

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 with a specific verb+resource+scope: 'Reads every directory listing waiting for this business, best fit first, in one read.' That is clearly distinguishable from generic siblings, but it never names or contrasts with nearby read tools such as waiting_read, discovery_read or place_open, so the agent must infer the boundary from the name alone.

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?

Usage is only implied by content: an agent gathering the envelope for submitting a listing form, or needing the `brief` text for a browser agent, can infer this is the tool. There is no explicit when-to-use, when-not-to-use, or named alternative among the ~47 siblings, which is a real gap given how many similarly named read tools exist.

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