create_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create a new collection' implies a write/mutation operation, the description doesn't disclose any behavioral traits: no information about permissions required, whether this is idempotent, what happens on conflicts, rate limits, or what the response looks like. The confusing note about 'created and updated' adds noise rather than useful behavioral context.

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 technically concise but poorly structured. The first part 'Create a new collection in PocketBase' is clear, but the second part 'note never use created and updated because these are already created' is confusing, appears to be a developer note that doesn't help the AI agent, and doesn't earn its place in the description. The two parts don't form a coherent whole.

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 complex mutation tool with 10 parameters (including nested objects), no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'collection' represents in PocketBase context, doesn't describe the outcome or response format, and the confusing note about 'created and updated' creates more questions than answers. The agent would struggle to use this tool effectively based solely on this description.

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 description coverage is 100%, so the schema already documents all 10 parameters thoroughly with descriptions, enums, and required fields. The description adds no parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify the confusing 'never use created and updated' note in relation to the schema parameters.

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') and the target system ('in PocketBase'), which provides a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'update_collection' or 'delete_collection' beyond the basic action, and the second part about 'never use created and updated' is confusing rather than clarifying.

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 like 'update_collection' or 'get_collection'. The confusing note about 'never use created and updated' appears to be a usage warning but is unclear and doesn't help the agent understand appropriate contexts or prerequisites for this creation operation.

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