taskbounty_login

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

With no annotations, the description carries the full burden and does well: it discloses the device-flow mechanism, return of URL and code, local credential storage, idempotent behavior when already authenticated, and that no API key is required upfront. It could add security/caution context around storing credentials locally, but the core behaviors are transparent.

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?

Four sentences, each earning its place: audience, mechanism, output, side effect, idempotency, and usage ordering. It is front-loaded with the most important purpose and contains no redundant or vague phrasing.

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 simple one-optional-parameter login tool with no output schema, the description provides enough context: what it returns, what it stores, when to run it, and how it relates to sibling tools. Nothing essential for selecting or invoking it correctly is missing.

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 single optional parameter is fully documented in the schema, so the baseline is 3. The description adds no additional meaning about client_name, but the schema description already explains it as an optional label shown on the approval screen, so nothing critical is missing.

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: 'authenticate to TaskBounty via a browser device flow.' It clearly distinguishes this login/setup tool from the many content-creation and bounty-management siblings by focusing on authentication and credential storage.

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 explicitly says 'Run this once before autopilot_enable or post_from_issue,' naming concrete dependent tools and establishing the prerequisite order. It also clarifies who should use it ('repo owners') and that it is not needed if already authenticated.

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