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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: requires a Bearer token, returns matching pockets with specific fields (IDs, titles, descriptions, creators, content types, pricing tiers), and does not retrieve content. It lacks some details like error cases, pagination behavior beyond limit, or rate limits, but covers the most critical aspects clearly.

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 moderately sized and front-loaded with the core purpose, then provides clear guidance on usage and parameters. Each sentence earns its place, though some details (e.g., specific return fields) could be considered slightly verbose. Overall, well-structured and readable without wasting words.

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 the tool's moderate complexity (4 params, no output schema, no annotations), the description is quite complete. It covers purpose, usage conditions, exclusions, auth requirement, parameter constraints, and return contents. Minor gaps like pagination mechanics or error handling exist, but these are not essential for basic correct invocation, and the context provided is sufficient for an agent to select and call the tool correctly.

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 parameters are well-documented in the schema. The description adds value by specifying natural language acceptable for query, that creator_email is case-insensitive exact match, and clarifies that at least one of query or creator_email must be provided, which is not fully captured in the schema. The limit parameter's default and max are already in the schema, so the description doesn't repeat that, but the 'at least one' constraint is essential added context.

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 tool searches a catalog by keyword, creator email, or content category, distinguishing it from siblings by explicitly noting it does NOT retrieve content and that pull_content should be used for actual content access. The verb 'Search' plus the resource 'Meta-Stamp Pockets catalog' provides a specific, actionable purpose.

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 says when to use: when an agent needs to discover available licensed content before pulling it, and knows the topic/creator but not the pocket ID. It also states what it does NOT do and directs to pull_content as the alternative, plus notes the requirement of a valid Bearer token and that at least one of query or creator_email must be provided.

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