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

Adds genuinely useful context beyond annotations: admin-only auth, immediate visibility to members, no notifications fired, and Skool auto-assigning the category color. It does not address duplicate handling or whether re-invoking creates a second category, which matters since idempotentHint=false. The destructiveHint=true annotation sits oddly against a create operation, but the description itself does not contradict it.

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?

Front-loaded with the action and audience, then the admin gate and behavior notes in short clauses. Minor redundancy between "Add a category to a group's feed" and "Adds a feed category," and the final sentence is a dense run-on, but overall it is tight.

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 create tool with no output schema, the description covers auth, visibility, notification side effects, and the one non-obvious parameter's meaning. Missing only what the call returns (e.g., the new category identifier) and duplicate-name behavior.

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%, so baseline is 3, but the description earns above baseline by explaining the semantic effect of who_can_post=admins (announcements-style posting restriction) rather than just restating the enum. It contributes nothing about sort or the color assignment being non-configurable in params, so not a 5.

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?

Specific verb + resource ("Add a category to a group's feed") with a concrete UI analogue ("as Settings, Categories, Add does") that removes ambiguity about what is created. It is clearly a creation tool, distinguishable from update_category/delete_category/list_categories by verb alone, though no sibling is named explicitly.

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?

States the admin prerequisite ("Admins only") and gives a decision rule for the who_can_post=admins variant (announcements-style, only admins post). It also licenses acting without confirmation. It stops short of naming update_category as the alternative for changing an existing category, so no explicit when-not guidance.

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