update_collection

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether changes are reversible, rate limits, or what happens when parameters are omitted (e.g., null values). The description provides basic functional information but lacks important behavioral context for a mutation tool.

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 efficiently structured with a clear opening statement followed by a well-organized parameter list. Every sentence serves a purpose, though the parameter explanations could be slightly more concise (e.g., 'view type' could list options without parentheses). Overall, it's appropriately sized and front-loaded with the main purpose.

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?

For a mutation tool with 6 parameters, no annotations, and no output schema, the description provides good parameter semantics but lacks important context about behavioral aspects, error conditions, and return values. It's adequate for basic usage but incomplete for a tool that modifies data without safety annotations or output documentation.

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. It clearly explains what each parameter does, including helpful context like 'omit for root collection' for parent_id and the specific view type options. This fully compensates for the lack of schema descriptions and adds meaningful interpretation beyond the basic schema.

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 action ('Update an existing collection') and resource ('in Raindrop.io'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'update_raindrop' or 'update_many_raindrops' beyond specifying it's for collections rather than raindrops.

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 like 'create_collection' or 'delete_collection'. It doesn't mention prerequisites (e.g., needing an existing collection ID) or clarify that this modifies existing collections rather than creating new ones, which is only implied by the name.

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