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

With no annotations provided, the description carries the disclosure burden and does well by stating that the operation is unsigned and that the reward returns while the fee remains spent. It does not explain the return transaction shape or all signing/auth mechanics, but it adds meaningful state-change context beyond the name.

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 description is compact and front-loaded with the tool category and action. Every clause contributes either scope, condition, or financial outcome.

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-parameter transaction-preparation tool with a fully documented schema, the description covers the action, eligibility condition, unsigned nature, and economic outcome. It could be slightly more complete about what the prepared unsigned result contains, but it is sufficient for correct tool selection.

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 100%, so the schema already fully explains the `job` and `wallet` parameters. The description does not add syntax or usage details for either parameter, so the baseline score of 3 is appropriate.

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 clearly identifies the tool as preparing an unsigned cancellation of a job-board posting by the poster. It adds the key condition that nobody has accepted the job, which distinguishes it from sibling board actions, though it does not explicitly name alternative tools.

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 states the usage context: the poster taking back a job that nobody has accepted. This gives clear when-to-use guidance, but it does not explicitly describe when not to use it or which sibling tool to use instead.

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