search_raindrops

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

No annotations provided, so description must carry burden. It states max per_page 50 and supported syntax, but does not disclose read-only nature, authentication needs, rate limits, or pagination behavior beyond per_page. Could be more informative.

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, no filler, front-loaded with purpose. Every sentence adds value.

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 4 simple parameters and existence of an output schema, the description covers main usage points: search syntax, special collection_id, per_page limit. Missing details on pagination and sorting, but adequate 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 descriptions cover 0% of parameters, so description must compensate. It adds meaning to collection_id (0 = search all) and per_page (max 50), but does not describe page or query parameters fully. Query is required but only generally described as 'search syntax'.

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 'Search bookmarks using Raindrop search syntax', specifying the verb and resource. It distinguishes from sibling list_raindrops by emphasizing search syntax and including special collection_id 0 meaning search all.

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 context on when to use: when search syntax is needed. Includes special collection_id value and max per_page. Does not explicitly mention alternatives or when not to use, but the context is clear enough.

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