Post organization collections

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write/non-destructive profile is known. The description adds nothing beyond that: no statement of what gets created, what fields are mandatory (the collection name/JSON body), whether a duplicate name overwrites, or what permissions are required for an org-scoped write.

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?

It is short and front-loaded, but at three words it is under-specified rather than efficient — there is no second sentence carrying the information a create-mutation tool needs. Brevity here is a deficit, not a virtue.

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 4-parameter mutation with 0% schema coverage, no output schema, and many near-identical sibling endpoints, the description is far too thin. Nothing tells the agent the response shape, the required payload, or the permission context, so correct invocation depends almost entirely on trial and error.

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?

Schema description coverage is 0% across four parameters (form, org_id, params, json_body) with completely opaque names and no types or descriptions. The description provides no parameter information whatsoever, so an agent has no way to know that org_id is the required organization identifier or what shape json_body must take.

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?

"Create a collection" states a specific verb and resource, but omits the organizational scope that the tool name implies and gives no hint of how it differs from the many sibling collection tools (post_collections_admin, post_collections_update, post_collection2_update, put_organization_collection_update). An agent can guess it creates something, but not which collection endpoint this is.

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?

There is no when-to-use guidance, no mention of prerequisites (organization membership, admin/owner role, collection management permission), and no routing to or away from any of the ~250 sibling tools. The agent must infer everything from the name.

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