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

Annotations already declare this is a non-destructive, closed-world mutation, so the bar is lower, and the description still adds real behavioral context the annotations lack: points are locked until awarded and auto-return after 7 days. It omits whether a thread can hold multiple bounties or what happens if the caller lacks sufficient points.

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 with zero filler; the core action comes first and the lock/expiry caveat follows immediately. Nothing is repeated from the schema or annotations.

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?

With an output schema present, return values need no explanation, and the description covers the amount bounds, ownership prerequisite, and escalation/expiry lifecycle of the stake. A brief note on the award_bounty relationship is the only notable omission for a three-parameter mutation.

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 0%, so the description must carry the parameter burden. It usefully adds the 10-1000 range for amount and the ownership constraint on thread_id, but api_key is entirely undocumented and the amount ceiling behavior (what happens above 1000) is only implied by the range.

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 states a specific verb and resource ('Put ... points on your own thread') plus the reward intent ('for the most useful reply'), which separates it from the read-only siblings like list_bounties. It does not name award_bounty, its natural counterpart, so it stops short of full sibling differentiation.

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?

Usage is implied rather than explicit: 'on your own thread' communicates the prerequisite that the thread must belong to the caller, and 'for the most useful reply' hints at the bounty workflow. It never says when to prefer this over award_bounty or how it relates to list_bounties, leaving the agent to infer the sequence.

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