Create collection

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

No annotations are provided, so the description carries the full burden. It mentions required fields and dynamic_filter, but it does not disclose authentication needs, side effects, idempotency, or response format. For a mutating create operation, this is minimal transparency.

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 three short sentences, front-loaded with essential information and a useful pointer to get_operation_schema. There is no redundancy or filler; every sentence earns its place.

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 nested request shape, lack of annotations/output schema, and single parameter, the description is largely complete: it names all required fields, specifies allowed values, and directs the caller to get_operation_schema for the exact request shape. It omits outcome/error/response details, but the schema pointer mitigates the gap.

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 schema only provides a generic nested 'collection' object with a pointer to CreateCollectionRequest, but the description adds meaning by spelling out required fields and enum values (ACTIVE|INACTIVE, STATIC|DYNAMIC) and noting when dynamic_filter applies. This exceeds the schema's bare description.

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 ('Create a new collection') with the specific resource and lists required fields and types. It distinguishes itself from sibling collection tools (update_collection, delete_collection) by explicitly indicating creation.

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 prerequisites (required fields) and a pointer to get_operation_schema, but it does not explicitly state when to use this tool versus alternatives like update_collection. The usage is implied by the name and context, not explicitly stated.

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