taskmarket_submissions

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

With no annotations, the description effectively discloses that access is public and anonymous, that the operation is read-only in effect, and that it never mutates task state by accepting or rejecting. It also lists returned fields, though it omits pagination or rate-limit behavior.

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 core description is front-loaded and efficient, covering purpose, access, return fields, and non-mutation behavior in three sentences. The final tip about earning_opportunities is tangential to invoking this tool and slightly distracts from otherwise tight structure.

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-parameter list tool with no annotations or output schema, the description provides enough context: what it returns, that it is public/anonymous, and that it cannot approve or reject work. No critical invocation detail appears 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 schema has 100% coverage and fully documents the single taskId parameter with its 0x+64 hex pattern. The description does not add parameter-level detail beyond implying that a TaskMarket task is required, so the schema does the heavy lifting.

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: it lists submissions on a TaskMarket task. It also names the review context and enumerates return fields, making it clearly distinct from taskmarket_get, taskmarket_search, and taskmarket_stats.

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 clearly states the context: human review of a deliverable before payment authorization, and explicitly says the tool never accepts or rejects work. It does not name a specific alternative for accepting/rejecting, but the boundary is clear.

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