tm_list_tasks

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

No annotations are present, so the description must carry the full burden of disclosing behavior. It states a list action, which implies a read-only operation, but does not disclose nuances like pagination, sorting, filtering, or what 'available' means. The description is too terse to provide adequate transparency for an unannotated tool.

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 a single concise sentence that immediately conveys the action and resource. It includes a clarifying parenthetical without unnecessary fluff. Every word earns its place.

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 list tool with full parameter coverage, the description gives a basic but not fully complete picture. It does not mention return format, pagination, or how to access task details via sibling tools. Without annotations, this leaves some ambiguity about behavior but remains adequate for a basic list operation.

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 description coverage is 100% for the single parameter 'limit' with a clear description 'max tasks'. The tool description adds no additional parameter context, but the schema already provides sufficient meaning, so the baseline 3 applies.

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 uses the specific verb 'List' with a clear resource 'TaskMarket tasks' and clarifies the task types in parentheses. This clearly distinguishes it from siblings like tm_get_task (fetch single task) and tm_my_submissions (list own submissions).

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 implies usage for browsing available tasks but does not explicitly contrast with siblings or state when to use this tool vs. alternatives. There are no exclusion criteria or alternative tool references, so the guidance is only implicit.

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