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

Goes well beyond the annotations: category name is validated before approval and fails immediately with the group's categories listed, posts are text-only, poll_options creates a poll under the text, and by default the call is gated on the owner's approval (which can be switched off). This is exactly the operational context annotations cannot express.

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?

Opens with the purpose, but the first two sentences say substantially the same thing ('Publish a post to the community feed in a category, as you' / 'Publishes a post to the group's feed in one of its categories, under your name'). The approval behavior is also split across the first and last sentences rather than consolidated.

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 five-parameter write tool with no output schema, the description covers the important unknowns: approval gating, fail-fast category validation, and the text-only media constraint. It does not touch on post visibility or what the call returns on success, but those are secondary.

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 the baseline is 3; the description adds real meaning by explaining that category names are checked up front and errors return the group's category list, that poll_options renders a poll under the text, and whom the author is.

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?

States a specific verb and resource ('Publish a post to the community feed in a category'), and clarifies authorship ('as you', 'under your name'). Sibling differentiation is only implicit via the name (create vs update_post/comment_on_post); nothing in the text explicitly routes away from those tools.

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?

Implies usage (publishing a new post into one of a group's categories) and warns that images/files are not supported, which steers an agent away from a wrong assumption. However, it never says when to prefer update_post or comment_on_post, nor any prerequisite such as needing a valid category or group membership.

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