search_bucket

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

With no annotations provided, the description carries the transparency burden. It discloses that search is semantic, covers all saved content types, returns summaries, and that get_item is needed for full detail. It does not mention pagination, ordering, or failure modes, but includes enough behavioral context for a basic understanding.

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?

Two sentences: the first states what the tool does, the second states the return behavior and points to get_item. No wasted words, information is front-loaded and easy to scan.

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 moderate complexity (2 params, no output schema), the description is reasonably complete. It defines the search scope, result nature (summaries), and next step for full detail. Minor gaps like default ordering or explicit limit behavior exist but are not critical.

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 both query and limit are already explained in the schema with examples. The description adds an example query in the text but does not provide additional semantic value beyond what the schema offers. 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?

The description clearly states a specific action ('Semantic search') and a specific resource ('everything saved in the user's Bucket'), listing content types. It distinguishes this tool from siblings like list_recent, get_item, and download_video by focusing on search across all saved 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?

The description implies when to use this tool: when you need semantic search over saved items. It explicitly tells the user to use get_item for full detail after receiving summaries, which is a useful pointer to an alternative. However, it does not explicitly mention when NOT to use it versus list_recent or other siblings.

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