update_raindrop

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

No annotations are provided, so the description must carry the full behavioral burden. It only conveys that the tool mutates an existing bookmark but does not disclose whether updates are partial or full replacement, what happens to unspecified fields, what response is returned, or any permission requirements. This is a significant gap for a write operation.

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 a single clear, front-loaded sentence with no filler. It efficiently conveys the core action and object, though it sacrifices behavioral detail for brevity.

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 8 parameters, no output schema, and no annotations, a one-line description is insufficient. An agent cannot determine partial-update semantics, how required vs optional fields interact, or what the API returns. The description should include at least basic context on update behavior and response format.

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?

All 8 parameters are documented in the input schema with descriptive text (e.g., 'Favorite status', 'Updated tags array'), so the schema already provides solid parameter semantics. The tool description adds no parameter-specific meaning, which matches the baseline for high schema coverage.

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 a specific verb ('Update') and resource ('existing bookmark') and notes the operation is by ID. This distinguishes it from create/delete siblings at a high level, though it does not explicitly name alternatives.

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 word 'existing' implies this tool modifies already-created bookmarks rather than creating or deleting them, so usage is somewhat evident. However, the description gives no explicit guidance about when to use this tool versus siblings, no prerequisites, and no exclusions.

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