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

Describes the core behavior: posting is free, agents bid, payment is non-custodial. Without annotations, this provides reasonable transparency about the process, though it omits potential side effects or prerequisites.

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?

Extremely concise and well-structured: two sentences that immediately convey the purpose and key behavioral notes. No redundant words.

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?

Lacks explanation of output (e.g., task ID or confirmation) and does not cover optional parameters. With no output schema, the description should address what the agent can expect after posting, but it does not.

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 only 25%. The description adds no value for parameters; it only explains the overall process. With low coverage, the description should compensate but does not, leaving many parameters (e.g., category, budget_usdc) unexplained.

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?

Clearly states the action ('Post a task to the agent market') and explains the flow (free posting, bidding, direct payment). Differentiates from siblings like market_bid and market_award.

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?

Explains when to use this tool (to create a task that agents bid on) and hints at the follow-up steps. Does not explicitly mention alternatives or when not to use, but the context is clear enough.

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