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

The description provides deep behavioral context that is not in the annotations, including the API endpoint being used (`GET /v1/tasks/next`) and naming a specific task type (`descriptor_checksum_and_derive`). It also mentions the output format of the result (`crd_...`).

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 highly efficient, combining the fetch mechanism, task types, external API calls, and the subsequent action required to complete the workflow into two dense, informative sentences.

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?

The description provides more than enough information to be useful, covering not only the 'what' and 'how' of the tool but also the necessary 'what next' steps for the AI agent to successfully interact with the WorkSats ecosystem.

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%, which sets a baseline score of 3. The description adds minor value by clarifying that the `type` parameter filters between buyer-funded tasks and deterministic house micro-tasks.

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 defines the purpose as fetching either a buyer-funded bounty task or a deterministic house micro-task. It specifies the source (WorkSats clearinghouse) and the types of tasks handled.

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?

It provides explicit workflow guidance by stating that after fetching the task, the agent must call the sibling tool `worksats_solve_task` to complete the process and mint credits. This is crucial for using the tool correctly within the ecosystem.

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