create_collection

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states the basic creation action, omitting any details about side effects, success/failure behavior, rate limits, required scopes, or whether the operation is idempotent. This is insufficient for an agent to understand the tool's runtime impact.

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 extremely concise at two sentences, with no redundancy. The first sentence clearly states the action and resource, and the second provides useful context. Every word earns its place, making it easy to parse quickly.

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?

The tool has no output schema, but the description does not mention what is returned upon success (e.g., the created collection object). It also lacks explanation of nested structures like parent_id or translated_content usage. Given the tool's moderate complexity (4 parameters, nested objects), the description leaves significant gaps that an agent would need to infer.

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 input schema has 100% description coverage on all parameters, so the baseline is 3. The description does not add extra meaning beyond the schema; it only provides context about collections being top-level. Since the schema already documents each parameter well, the description meets the minimum but does not enhance parameter understanding.

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') and the resource ('a new Intercom Help Center collection') and distinguishes it from sibling tools like 'create_article' or 'delete_collection' by specifying that collections are top-level categories. The verb+resource combination is specific and unambiguous.

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. It does not mention prerequisites, when not to use it, or how to choose between creation and other operations (e.g., update_collection). The agent receives no contextual cues for decision-making.

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