search_bookmarks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply repeats the tool's name and mentions 'advanced filters' without detailing how search works, what fields are searched, or any side effects/limitations. This adds minimal value beyond the tool's name.

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 single, front-loaded sentence with no unnecessary words. It is concise and scannable, though 'advanced filters' is slightly vague and could be more specific without adding length.

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?

Despite having a rich output schema and fully documented parameters, the description fails to provide necessary context about when to use this tool over siblings like 'get_bookmarks'. It does not clarify the scope of search (e.g., user's bookmarks vs. all) or any special behavior, making it incomplete for an agent to select 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?

The input schema provides 100% parameter description coverage, so the baseline is 3. The description's mention of 'advanced filters' adds no specific meaning beyond what the schema already documents for parameters like q, shared, and unread.

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 uses the specific verb 'Search' with the resource 'bookmarks' and adds 'with advanced filters', which clearly indicates the tool's function. However, it does not explicitly distinguish itself from the sibling 'get_bookmarks' tool, which might also search or list bookmarks.

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 no guidance on when to use this tool vs. alternatives such as 'get_bookmarks' or 'check_bookmark'. It implies usage through the phrase 'advanced filters' but does not state any exclusions or preferred contexts, leaving the agent to infer when this tool is appropriate.

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