create_sync_collection

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

Annotations already communicate that this is a mutating, idempotent, non-destructive operation, and the description is consistent with them. The description adds little behavioral nuance beyond the verb 'add' and the payload-discovery instruction; it doesn't mention duplicate handling, partial failures, or authentication requirements.

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 short, front-loaded with the core action, and contains no filler. The 'POST /sync/collection' line is somewhat redundant with the tool's name/purpose, but the overall structure is efficient.

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?

Annotations and the presence of an output schema cover safety and return shape, but the opaque body leaves a major gap. The pointer to 'the matching GET or /schema endpoint' is vague given the many sync collection siblings, and the description doesn't convey what a valid collection-sync payload should contain or how additions behave.

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 only parameter, body, is an opaque additionalProperties object with 0% schema description coverage. Calling it a 'request payload' mostly restates the schema, and telling the agent to read the schema endpoint is a workaround rather than actual parameter semantics. The description does not compensate for the empty body 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 states a specific action ('Add items') and a resource ('collection'), which matches the tool name and distinguishes it from the obvious counterpart create_sync_collection_remove. It doesn't explicitly mention 'sync' or name a sibling, so it's clear but not fully differentiated.

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 use case is implied: use this when adding items to a collection. The description also gives a prerequisite ('Read the matching GET or the /schema endpoint first'), which is helpful. However, it doesn't explicitly say when to prefer this over related sync create/update/remove tools, nor does it name the exact matching GET.

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