searchBookmarks

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'advanced filters' but doesn't describe pagination behavior (implied by 'page' and 'perPage' parameters), rate limits, authentication requirements, or what happens when no results are found. For a search tool with 10 parameters, this is inadequate behavioral context.

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 extremely concise at just 5 words, front-loaded with the core purpose. Every word earns its place, with no redundant information or unnecessary elaboration. This is a model of efficient description writing.

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 search tool with 10 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a successful search, what the return format looks like, or how to interpret the various filter parameters in practice. The agent would need to guess about important behavioral aspects.

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 schema already documents all 10 parameters thoroughly. The description adds no additional parameter semantics beyond mentioning 'advanced filters' generically. The baseline of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 'Search bookmarks with advanced filters' clearly indicates the verb (search) and resource (bookmarks), but lacks specificity about what constitutes 'advanced filters' and doesn't differentiate from sibling tools like 'getBookmarks' or 'exportBookmarks'. It's vague about the scope of search capabilities beyond mentioning 'advanced filters'.

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?

No guidance is provided about when to use this tool versus alternatives like 'getBookmarks' (which appears to be a simpler retrieval tool) or 'exportBookmarks'. The description mentions 'advanced filters' but doesn't clarify what makes this tool preferable to other bookmark-related tools in specific contexts.

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