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

With no annotations, the description carries the full burden and delivers: Bearer-token auth with HTTP 402 on failure, metered charging at owner_price with a platform default, royalty logging, the full receipt shape, distinct refusal outcomes (registration_required, payment_required, catalog_closed), and the special listing-only delivery case. Nothing material about side effects or failure modes is left undisclosed.

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 description is long but front-loaded with purpose, then usage, then auth/economics, then edge cases, so a reader gets the essentials first. Most of the dense receipt and content_hash detail is justified because there is no output schema. A small penalty for the run-on single-paragraph format that would read better as structured blocks.

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 paid, authenticated pull tool with no output schema, the description compensates fully: it specifies the return payload, provenance metadata, receipt shape and verify_url, every refusal path, and the listing-only variant. An agent has everything needed to call it and interpret both success and failure.

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 coverage is 100%, so both parameters are already documented, and the description repeats the pocket_id 24-character hex detail that the schema already contains. The optional 'query' parameter is never mentioned in the description, so it adds essentially nothing beyond the schema. Baseline 3 is correct.

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 and resource ('Pull licensed creator content from a specific pocket by ID') and immediately distinguishes itself from the sibling tools by naming search_pockets and list_pockets as the browsing/discovery path. An agent can identify the operation without opening the schema.

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?

Explicitly states when to use it (generation, RAG, inference on verified provenance-tracked content), when not to use it ('Do NOT use for browsing or discovery'), and adds a licensing constraint (separate training license). This is about as complete as usage guidance gets.

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