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

Annotations already carry destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is documented in structured data. The description adds one genuinely new behavioral fact, the admin-only permission requirement, but says nothing about limits on category count, duplicate-name behavior, or what a failed call looks like.

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 short sentences, front-loaded with the action and followed by the permission constraint. Nothing is padded, though the extreme brevity leaves gaps that a third sentence could have closed.

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 destructive, non-idempotent mutation with fully documented parameters and no output schema, the description is just barely adequate. It covers what and who, but not what the call returns or how the destructive hint manifests, leaving the agent to rely on annotations for the risk picture.

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 description coverage is 100% and both enums (sort, who_can_post) are documented in-schema with defaults, so the description is not required to compensate. 'group's feed' only loosely gestures at the required group parameter, adding no syntax or format detail beyond the schema.

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, which distinguishes it from the sibling update_category, delete_category and list_categories. Scope is narrowed to a group's feed, but the description never names those siblings 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?

'Admins only' gives a real precondition, which is more than most sibling tools offer. However, it never states when to choose this over update_category or when a category already exists, so the agent must infer the create-vs-update boundary from the tool name alone.

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