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

With no annotations, the description carries the full burden and excels. It discloses the Bearer token requirement, the HTTP 401 on unauthenticated requests, the metered charge ($0.001–$0.25), royalty distribution logging, and the return payload with provenance metadata. This is comprehensive and goes beyond typical descriptions.

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 a compact paragraph of five sentences, each serving a distinct purpose: purpose, when to use, when not to use, auth/cost, and return value. There is no fluff or redundancy, making it efficient and well-structured.

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?

Given no output schema, the description appropriately explains the return value ('full content payload with provenance metadata including creator attribution and license terms'). It also covers auth, cost, and usage context, making it complete for a tool with this complexity.

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 the baseline is 3. The description mostly repeats what the schema already provides (e.g., pocket_id is a 24-character hex string) without adding significant new parameter semantics. It does reinforce the source of pocket_id (from search_pockets or list_pockets), but this is also in 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?

The description opens with 'Pull licensed creator content from a specific pocket by ID,' which is a specific verb+resource+identifier. It also explicitly differentiates from siblings by stating 'Do NOT use for browsing or discovery — use search_pockets or list_pockets instead,' making the purpose unmistakable.

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?

The description provides explicit when-to-use guidance: 'Use this tool when an AI agent needs to retrieve verified, provenance-tracked content for generation, RAG, or training purposes.' It also gives a clear exclusion: 'Do NOT use for browsing or discovery' and names the alternative tools. The authentication prerequisite is also stated.

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