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

Annotations only declare readOnlyHint=false, so the description usefully adds that authentication is required on the request and that tags feed the matcher. It says nothing about what creation returns, whether reward is escrowed, or what happens on expiry, leaving the mutation's effects largely opaque.

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?

Two short sentences with the core action front-loaded and no filler. The telegraphic style borders on under-specification, but nothing is wasted.

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 seven-parameter creation tool with zero schema descriptions, no output schema, and minimal annotations, the description is too thin to call correctly. An agent cannot confidently populate reward, category, no_house, or expires_in_hours from this text.

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 0%, so the description carries the full burden, yet it only explains one of seven parameters ('tags: optional list of up to 8 short words'). The meanings of reward, category, no_house, description, and expires_in_hours are left entirely to inference, with no_house especially cryptic.

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?

States a specific verb and resource ('Post a task') and clarifies the domain with '(need or offer)', so an agent knows it creates a task listing rather than reading one. It does not, however, distinguish itself from close siblings such as post_need_offer or create_post.

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 gives no when-to-use guidance and names no alternatives, despite siblings like post_need_offer and create_post that plausibly overlap. The only contextual hint is that the Bearer key is required on the /mcp request.

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