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

Discloses auth requirement (Bearer token), pagination, and that it does not retrieve content. With no annotations provided, the description fully carries the behavioral disclosure burden.

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?

Four sentences each earn their place: purpose, usage, behavioral boundary, and auth/parameter context. Front-loaded 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?

Covers auth, pagination, filtering, return fields, and contrasts with siblings. No gaps for a simple list tool with optional parameters.

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% and the description adds no substantive parameter semantics beyond what schema already provides. Baseline 3 is appropriate.

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?

Clearly states 'List all available content pockets' and distinguishes from siblings by explicitly referencing search_pockets for specific topics and pull_content for retrieval.

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?

Provides explicit when-to-use (browse full catalog, filter by creator) and when-not-to-use (prefer search_pockets for topics, pull_content for content retrieval) guidance.

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

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.

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

No annotations provided, so description carries full burden. It discloses authentication requirement ('Requires a valid Bearer token'), describes return fields ('IDs, titles, descriptions, creators, content types, and pricing tiers'), and mentions pagination control via limit. Could further clarify pagination behavior if results exceed limit.

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?

Description is a single paragraph of 5 sentences, front-loaded with purpose and usage. While concise and clear, it could be slightly better structured with bullet points or separate paragraphs for even easier scanning.

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 tool with 3 parameters, no output schema, and no annotations, the description covers all necessary context: purpose, usage guidelines, parameter behavior, authentication, and relationship to siblings. It is complete for an AI agent to understand when and how to use it.

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% with descriptions for all three parameters. The description adds value by explaining what the query parameter accepts ('natural language search terms, creator names, or category keywords'), that content_type is optional with examples, and specifies the default and maximum for limit.

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 clearly states the action ('Search the Meta-Stamp Pockets catalog') and the resource ('by keyword, creator name, or content category'). It distinguishes itself from siblings by noting that this is for discovery before pulling content, and explicitly says 'Does NOT retrieve content — use pull_content with the returned pocket_id to access actual content.'

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?

Provides explicit guidance: 'Use this tool when an AI agent needs to discover available licensed content before pulling it. Ideal for finding relevant pockets when the agent knows what topic or creator it needs but not the specific pocket ID.' It also tells the agent what not to use it for and directs to pull_content.

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