Create a category (usable on watchlist accounts, posts and assets). Only the org owner or an admin can manage categories.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Category name | |
| color | No | Optional hex color like #3B82F6 (default blue) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds a meaningful permission constraint—only org owner or admin can manage categories—which is not present in annotations. It also implies a mutating operation consistent with readOnlyHint: false. However, it does not describe duplicate-name behavior, whether categories are global, or what happens after creation.
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?
Two concise sentences deliver the core action, applicable resources, and permission requirement without extra filler. The most important information is front-loaded.
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 is low-complexity with only two simple parameters and no nested objects, and the schema covers the parameter details. The description covers purpose, resource applicability, and authorization, but does not mention return values or duplicate-handling behavior, leaving a minor 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?
Both parameters are fully described in the schema, including the optional color default. The description adds no parameter-specific meaning beyond the schema, so baseline scoring is appropriate.
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 identifies the operation as creating a category, which is a specific verb and resource. It distinguishes the tool from set-like category assignment tools by noting the category is 'usable on watchlist accounts, posts and assets.' It does not explicitly name sibling alternatives, but the action and resource are 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 states a clear usage context: categories are used on watchlist accounts, posts, and assets, and only org owners or admins can manage them. It does not explicitly say when to choose this over set_post_category, set_account_category, or other assignment tools, leaving some routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct target resource/action, and the descriptions are unusually explicit about differences (e.g., 'Distinct from the watchlist', 'Separate list from list_tags'). A few pairs are still easy to confuse without careful reading: delete_folder vs delete_folders differ only by singular/plural, and the three download-URL tools (get_post_download_url, get_asset_download_url, get_my_account_post_download_url) plus the category/tag families require attention to pick correctly.
The snake_case verb_noun pattern is followed consistently throughout (list_*, get_*, create_*, update_*, delete_*, set_*, tag_*). Minor deviations: archive_folder and archive_my_accounts also perform restore despite their names, delete_folder/delete_folders split one operation by cardinality, and tag_posts/tag_my_account use a different verb style than the set_* family for metadata mutations.
At 56 tools, this far exceeds the 25+ threshold for 'too many,' even though the server spans multiple subdomains (watchlist, analysis, assignments, folders, my accounts, assets, Drive, categories/tags). Obvious consolidation candidates exist — delete_folder/delete_folders, the three download-URL getters, and the parallel list_my_account_* listers — and the sheer surface is heavy for an agent to navigate.
Core workflows are thoroughly covered with no dead ends: watchlist → analyze → assign → folder → track → approve has full lifecycle support, including reversible archive vs permanent delete choices. Minor gaps exist but are work-aroundable: no create/update for my accounts or models (app-side OAuth/admin only), no way to delete a viral post or a post note, and asset upload only happens in the app.
