update_raindrop

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 correctly identifies this as an update operation, it doesn't mention important behavioral aspects: whether this requires authentication, what permissions are needed, whether the update is atomic or partial, what happens with null values, or what the response looks like. The description only lists parameters without explaining the tool's behavior.

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 with a clear purpose statement followed by a parameter list. Each parameter explanation is concise and informative. However, the formatting with bullet points could be improved for readability, and some parameter explanations could be slightly more efficient (e.g., 'New description/excerpt' for excerpt is redundant).

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 complexity (11 parameters, mutation operation) and lack of both annotations and output schema, the description is moderately complete. It excels at parameter documentation but misses critical behavioral context about authentication, error handling, response format, and relationship to sibling tools. For a mutation tool with no structured metadata, 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 provides excellent parameter semantics despite 0% schema description coverage. For all 11 parameters, it adds meaningful context beyond the schema: explaining what 'important' does ('Set to True to mark as favorite'), clarifying 'order' behavior ('set to 0 to move to first place'), and defining purpose for each field. This fully compensates for the lack of schema 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: 'Update an existing raindrop (bookmark) in Raindrop.io'. This specifies the verb ('update'), resource ('raindrop'), and context ('Raindrop.io'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'update_collection' or 'update_many_raindrops' beyond the resource name.

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. There are no mentions of prerequisites (like needing an existing raindrop ID), comparison to sibling tools (like 'update_many_raindrops' for bulk operations), or specific scenarios where this tool is appropriate versus others in the server.

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