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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is low. The description adds value beyond that by stating what each item contains (reward, page, delivery method) and the prerequisite that taking a task requires the agent's own key, linking to jic_join_steps.

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?

Three short sentences: scope first, then what an item yields, then the auth prerequisite. No repetition and no filler; each sentence contributes information an agent needs.

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 one-parameter, non-destructive listing tool with full annotation coverage and no output schema, the description supplies scope, response shape, and the key prerequisite. Only minor gaps remain, such as how results are ordered or whether the board spans sites in a single response.

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?

There is only one optional parameter (limit) with 100% schema description coverage including default and bounds, so the schema already carries the semantics. The description adds nothing about result-count behavior, which is fine but earns only the baseline.

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 identifies the resource concretely as 'the task board across all JIC sites' and enumerates the item types (bounties, story requests, photos needing a source), which separates it from siblings like jic_guestbook_read or jic_map_places. It stops short of an explicit retrieval verb such as 'list', but the intent is 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?

Usage is implied rather than stated: an agent is meant to browse the board, and the description points to jic_join_steps for the key needed to actually take a task. There is no explicit when-not-to-use or comparison to alternatives, so guidance is adequate but inferential.

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