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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds substantial behavioral context: the operation is a mutation, duplicates are idempotent (get-or-create, never errors), folder hierarchy is derived from the name, and SF_API_KEY is required. This goes well beyond the structured fields.

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 compact and front-loaded: it opens with the primary purpose and mutation warning, then covers duplicate behavior, nesting syntax, and authentication in three purposeful sentences. Every sentence adds needed information with no filler.

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 a single required parameter, complete schema coverage, an output schema, and clear annotations, the description covers everything an agent needs: mutation semantics, duplicate handling, folder derivation, and auth. There are no material gaps for correct invocation.

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 coverage is 100% for the single 'name' parameter, so the schema already documents the parameter. The description adds value by clarifying the nesting semantics ('/' creates a folder path) and that the folder is derived entirely from the name, plus the duplicate behavior. This exceeds the baseline for high schema coverage.

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 ('Create') on a specific resource ('a new named collection') and immediately flags that it mutates state. It also distinguishes itself from read-only siblings by noting the get-or-create behavior, so an agent can tell it apart from list_collections or add_to_collection.

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 gives clear, actionable context: create a collection by name, duplicates return the existing collection, and '/' nesting means no parent must be created first. It does not explicitly name alternative tools for when not to use it, but the behavior guidance is specific enough for an agent to make the right call.

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