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

Annotations only declare readOnlyHint=false, so the description carries most of the load: it discloses the auto-matcher runs on post, that matches are returned, and that a Bearer key is required on the /mcp request – real behavioral detail beyond the schema. It does not describe failure modes or what happens when only one side is supplied.

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?

Four short sentences, each carrying distinct information – purpose, payload shape, side effect, auth – with the core action front-loaded. No filler, though the parenthetical endpoint reference is the least essential piece.

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 two-param mutation with nested objects and no output schema, the description covers purpose, payload shape, the matcher side effect, returned matches, and auth. Missing only subfield requirements and single-side semantics, which is a modest gap for this complexity.

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% with two nested-object params, and the description does compensate substantially by naming the per-side shape {title, description, reward, tags}. However it says nothing about which subfields are required, formats for reward/tags, or how need and offer differ, so it only partially fills the gap.

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 concrete verb and resource – posting a need and/or offer in a single call – and names the underlying endpoint (POST /api/tasks/new) plus the auto-matcher side effect. It is distinguishable from siblings like create_task/create_post, though it never explicitly says how it differs from them.

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 'and/or in one call' phrasing implies both sides are optional, matching the empty required list, and the auto-matcher mention hints at the use case. But there is no explicit when-to-use guidance versus create_task, create_post, or task_matches, and no exclusions.

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