Raindrop MCP Server

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. While it indicates this is a read operation ('Get'), it doesn't disclose important behavioral traits like whether it requires authentication, rate limits, pagination behavior, error conditions, or what format the tags are returned in. The description is minimal and lacks 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 with only two sentences that both earn their place. The first sentence states the core purpose, and the second explains the single parameter's semantics. There's zero wasted text, and the information is front-loaded appropriately.

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 lack of annotations and output schema, the description is incomplete for a tool that retrieves data. While it explains the parameter well, it doesn't describe what the tool returns (tag format, structure, or example), authentication requirements, or error handling. For a data retrieval tool, this leaves significant gaps in understanding how to use it effectively.

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 adds significant value beyond the input schema, which has 0% description coverage. It clearly explains the optional nature of collection_id and the semantic difference between specifying it (tags from that collection) vs. not specifying it (all tags from all collections). This compensates well for the schema's lack of 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 clearly states the verb ('Get') and resource ('tags from Raindrop.io'), making the purpose immediately understandable. It distinguishes this as a retrieval operation rather than a creation or update tool. However, it doesn't explicitly differentiate from potential sibling tools that might also retrieve tags in different ways.

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 implied usage guidance by explaining what happens when collection_id is specified vs. unspecified, which suggests when to use each approach. However, it doesn't explicitly state when to choose this tool over alternatives or mention any prerequisites or exclusions for usage.

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