update_bounty

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

No annotations are provided, so the description carries full burden. It states the intended action but does not disclose additional behavioral traits such as side effects, permissions required, or idempotency. For a simple update, this is adequate but not thorough.

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 with no wasted words. Key information is front-loaded ('Use this when...'). Structure is efficient and easy 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 lack of output schema and annotations, the description covers purpose and key parameters but omits return value, error conditions, or behavior beyond the action. For a simple tool, this is marginally complete but could be richer.

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?

With 0% schema description coverage, the description adds value by explaining that expiry is a unix timestamp and that bounty_id is required (though already in schema). It does not detail the meaning of bounty_id or constraints, but the added explanation is helpful.

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?

Description explicitly states 'extend a bounty's expiry', which is a specific verb+resource action. It clearly distinguishes from siblings like close_bounty (closing) and get_bounty (viewing), making the tool's purpose unambiguous.

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 direct when-to-use guidance ('when you need to extend a bounty's expiry') and references sibling tools (get_bounty, close_bounty) as alternatives. Lacks explicit exclusions (e.g., when not to use), but the context is clear.

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