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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the resource is 'public' (no user-scoped auth implied) and framed as a 'card', but says nothing about behavior when the slug is unknown or malformed (error vs null).

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?

A single front-loaded sentence with no filler; the resource and the lookup key come first. It is efficient, though its brevity borders on under-specification rather than tight conciseness.

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?

Output schema exists, so return shape need not be described, and the tool is a simple single-parameter read. Still missing is any note on where to obtain a canonical slug and how a not-found case surfaces, which an agent needs to chain calls correctly.

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 0%, so the schema only gives `listingSourceSlugId: string` with no meaning. The description partially compensates by clarifying that the expected value is a canonical slug rather than an arbitrary id, but it gives no format, source, or example of where such a slug comes from.

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?

States a specific verb ('Read') and resource ('public listing-source card') plus the lookup key ('canonical slug'). It is clear what the tool returns, though it never names or distinguishes itself from the sibling searchPublicListingSources, which is the obvious alternative path to the same resource.

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 no explicit guidance on when to call this versus searchPublicListingSources, and no mention of the precondition that a canonical slug must already be known. The phrase 'by its canonical slug' only faintly implies the requirement.

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