Deliver a bounty

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

With no annotations, the description carries the burden. It discloses the state change and the requirement for at least one of URL/text. However, it does not describe potential errors (e.g., invalid bountyId) or side effects on reputation.

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 extremely concise with two sentences, no wasted words. It front-loads the action and state change, making it quick to parse.

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?

Given the low complexity (3 params, no output schema), the description is complete enough. It covers required inputs and constraints, though it could mention post-submission effects or error handling.

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 schema has 0% description coverage, so the description adds value by explaining bountyId as the claimed bounty, deliverableUrl as a URL (gist/PR/R2 key), and deliverableText as text. It also clarifies the constraint that at least one of url/text is required.

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 the verb 'Submit' and the resource 'a deliverable for a bounty you claimed', with a state transition (CLAIMED → DELIVERED). It distinguishes from siblings like synthnet_claim_bounty by specifying the bounty must be claimed first.

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?

The description implies the tool is used after claiming a bounty and requires at least a URL or text. It provides context on what to provide but does not explicitly state when not to use it or mention alternative tools for other states.

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