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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value by asserting the receipt is 'authoritative' (canonical source of truth, not cached or prepared state) and that reading does not retry publication, i.e. no side effects on delivery.

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 tight sentence with the resource and the key constraint front-loaded; nothing is padding. It is slightly jargon-dense ('native publication receipt'), but no sentence is wasted.

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?

For a two-parameter read with a full annotation set and an output schema covering the return shape, the description supplies enough to call it correctly. Only edge-case behaviour (no receipt yet, unknown publication_id) is left unstated.

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% and the description never mentions workspace_id or publication_id, nor any format, scoping or lookup rules for them. The two parameters are self-evidently named IDs, which softens the gap, but the description does nothing to compensate for the missing schema documentation.

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 a specific resource ('native publication receipt and per-destination outcome'), which clearly separates it from prepare_social_publication and publish_social_draft. It does not explicitly name any sibling, so the differentiation is inferred rather than stated.

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?

'Without retrying publication' implies the intended context: check status instead of re-triggering a publish. However, there is no explicit when-to-use guidance, no mention of what to call when no receipt exists yet, and no reference to the neighbouring publication tools.

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