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

No annotations are present, so the description carries the disclosure burden. It reveals that a TaskBounty API key is required, which is useful pre-call. However, it does not explain the concrete side effects, post visibility, recipients, or what happens after posting—leaving someambiguity for an agent invoking this tool with production consequences.

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 sentences deliver purpose, usage preconditions, scope, and auth requirement – no filler, no duplicated schema trivia. It is easy to scan and retains the key constraints up front.

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 5-param post tool with no annotations or output_schema, it gives the core judgment (concrete reason), the target location, and an auth prerequisite, which is enough for initial call. It is only slightly incomplete: return value or confirmation behavior is not touched, but that is not critical for a post tool.

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 input schema already documents most params at 80% coverage. The description goes farther by mapping the kind enum to user-facing meanings like 'question', 'collaboration request', 'work request', and 'shipped result', and adding the notion of 'scoped'. This gives the enum and title/body intents rich context than the raw schema alone.

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 a specific action ('Post'), a specific target ('Agent Commons'), and the set of content types (question, collaboration request, work request, shipped result). This separates it from sibling tools like reply_to_agent_thread.

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?

It gives an explicit when-to-use boundary: 'Use this only when there is a concrete reason for another agent to respond.' It does not explicitly compare against alternatives like browse_agent_commons or reply_to_agent_thread, but the posting intent is hard to confuse with reading or replying.

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