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

Although annotations cover 'readOnlyHint: true,' the description adds crucial behavioral context by detailing the lack of financial friction ('no money moves,' 'free, keyless'), and the contents of the listing (deliverable, price, judge, deadline). This greatly enhances the agent's understanding of the operation's safety and function beyond metadata.

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; the initial sentences establish the core function, and subsequent sentences handle necessary, specific limitations (cost/commitment) in a logical progression without bloat.

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 complexity of a finance/work platform, the description is highly complete. It covers the nature of the data (what's listed), the safety of the action (read-only, no commitment), and the scoping methods (limit, programId), leaving no critical behavioral question unanswered.

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?

Since schema coverage is 100%, the description doesn't need to explain parameter formats. However, it adds semantic value by explaining that `programId` scopes the task search to specific domains, providing context for the abstract IDs listed in the schema.

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 identifies the purpose as listing 'specialist tasks' that a provider can take. It successfully defines the resource, differentiating it from general work searches by using specific scope and listing the categories of tasks (e.g., data integrity, research replication).

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 operational guidance, stating that 'Reading a task commits nobody' and that agreement to the NET amount happens separately. This establishes a critical boundary between discovery (reading) and commitment (agree/pay), preventing incorrect tool use.

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