get_raindrops

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 describes the tool as a read operation ('Get'), which implies it's non-destructive, but doesn't explicitly state this. It mentions pagination behavior (page/perpage) and special collection_id values (0, -1, -99), adding useful context. However, it lacks details on rate limits, authentication needs, or error handling, leaving gaps for a tool with 6 parameters.

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 well-structured and appropriately sized. It starts with a clear purpose statement, followed by a bullet-point-like list of parameters with explanations. Every sentence adds value, with no redundant information. It could be slightly more concise by integrating the purpose and parameter list more seamlessly, but it's efficient overall.

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 the tool's complexity (6 parameters, no annotations, no output schema), the description is moderately complete. It thoroughly documents parameters but lacks information on return values, error cases, or behavioral traits like rate limits. For a read-only tool with multiple options, this leaves the agent without full context on what to expect from the output.

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 description provides extensive parameter semantics beyond the input schema, which has 0% description coverage. It explains each parameter's purpose, special values (e.g., collection_id: 0 for all, -1 for unsorted), defaults (sort: '-created'), constraints (perpage: max 50), and options (sort: list of values). This fully compensates for the schema's lack of descriptions.

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 the tool's purpose: 'Get multiple raindrops from a Raindrop.io collection.' It specifies the verb ('Get') and resource ('raindrops'), but doesn't explicitly differentiate it from sibling tools like 'get_raindrop' (singular) or 'update_many_raindrops' (write operation). The description is specific but lacks sibling differentiation.

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 versus alternatives. It doesn't mention sibling tools like 'get_raindrop' (for single raindrops) or 'update_many_raindrops' (for modifications), nor does it specify prerequisites or exclusions. The only implied usage is for fetching multiple raindrops, but this is basic and insufficient.

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