post_from_issue

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

With no annotations provided, the description carries the full burden and does this well. It reveals that payment is not handled here, that the response returns a funding URL to open in the browser, that triage sizing is automatic unless bounty_usd is passed, and that the tool is intended for repo owners. These are meaningful behavioral traits beyond what the schema shows.

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?

The description is compact and well-structured: purpose first, then default behavior, payment limitation, alternative tool, and login prerequisite. Every sentence adds necessary context with no filler.

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 two-parameter tool with no output schema, the description covers what the agent needs: how to invoke it, the optional amount behavior, what the response will provide, the prerequisite login step, and the relevant alternative for recurring use. Nothing essential is missing for correct invocation.

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 schema already documents both issue_url and bounty_usd. The description's mention of automatic triage sizing when bounty_usd is omitted essentially repeats the schema's explanation, adding no significant new parameter semantics.

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 states a specific action ('post a one-off bounty') and the exact resource ('existing GitHub issue URL'). It also differentiates from autopilot_enable by explicitly noting this is for one-off bounties, not unlimited fixes.

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?

Provides explicit guidance on when to use an alternative: 'For unlimited fixes on a repo, prefer autopilot_enable.' It also states a required prerequisite ('Requires login (run taskbounty_login first)') and clarifies a key limitation ('Payment is NOT handled here'), all of which help an agent decide whether this tool is appropriate.

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