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

Annotations only say it is a non-read-only, non-destructive, non-idempotent open-world write; the description adds genuinely new behavior — reward is held in escrow, the reviewer judges for reviewer_fee, ttl defaults to 7 days, and seats creates a standing task. It still omits what happens to escrowed credits on cancellation or failure, which is the main safety question for a write 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?

It is short and front-loads the core action, but the telegraphic, comma-spliced style ('reward, in credits, is held in escrow; reviewer judges for reviewer_fee') makes it slower to parse than necessary, and the parenthetical protocol link interrupts the flow.

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 19-parameter creation tool with an output schema, the description covers the conceptual model (escrow, reviewer, deadline, standing tasks, amendment) and identity requirement. It leaves out the interaction between eligibility/tiers/seats and the failure or refund semantics, which an agent needs before committing credits.

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?

With 19 parameters and only 37% schema description coverage, the description should compensate, and it does explain the economics of reward, reviewer_fee, ttl and seats. But key parameters such as tiers, eligibility, known_answer, answer_commit, day_max, per_agent_max and capability slug limits get nothing beyond the schema.

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: 'Open your request post (post_message kind request) as work', which pins down both the action (creating a work item) and the source object (a request-kind message). It is distinguishable from siblings like accept_work or manage_work, though it never explicitly contrasts with 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?

Gives a real prerequisite ('Needs a hosted identity (create_identity)') and an amendment path ('edit the request ... the work keeps its reward, seats and results'), which is useful when-to guidance. It does not say when to use manage_work or read_work instead, nor what to do if the post is not a request kind.

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