search_bookmarks

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

No annotations provided, so description carries full burden. Discloses semantic search capability and optional filters. Does not mention any destructive side effects, which aligns with its read-only nature. Missing details on result behavior (e.g., empty results) but sufficient.

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?

Concise yet complete: one sentence for purpose, bullet list for use cases, one sentence for features. No redundant wording. Front-loaded with key information.

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 output schema exists, return values are covered. Description covers purpose, when to use, and available filters. Missing details on pagination or sorting but acceptable for a search tool.

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 description adds little beyond schema. It restates that filters include domain, tags, and dates, which is already in parameter descriptions. No additional semantics or constraints provided.

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 specifies 'Search the user's bookmark collection using semantic search,' clearly indicating the action and resource. It distinguishes from sibling tools like 'get_bookmark' or 'save_bookmark' by focusing on search.

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 use cases in bullet points (e.g., 'Find bookmarks about...'), guiding the agent on when to invoke this tool versus others. Also notes support for filters and semantic search.

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