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

No annotations are provided, so the description carries the full behavioral burden, yet it only states the retrieval action. It says nothing about permission/identity requirements implied by author_npub and operator_npub, nor how a missing or unpublished campaign is reported. 'Retrieve' implies read-only, but that is the extent of the disclosure.

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 short sentence with no filler and the key qualifier ('published') placed before the resource. It is efficient, though the extreme brevity is closer to under-specification than to crispness.

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 values need not be described, and the input schema fully documents parameters. What is missing is the routing information (why this over list_campaigns) and the identity/permission context implied by the required npub parameters, leaving the definition merely adequate for a read tool.

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%, so all four parameters (including the json/markdown format option) are already documented in the schema. The description adds no syntax, format, or identity-resolution detail beyond that, so the baseline of 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 gives a specific verb ('Retrieve') and resource ('a published pricing campaign'), so the agent knows the operation and object. It does not, however, distinguish this single-campaign fetch from the sibling list_campaigns or publish_campaign, which would require the reader to infer the difference from the names 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?

There is no explicit when-to-use guidance and no mention of alternatives, despite list_campaigns being an obvious sibling that overlaps in subject matter. The word 'published' faintly implies unpublished drafts are excluded, but this is left for the agent to infer rather than stated.

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