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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with an emphatic 'Nothing is posted' — valuable because the 'create_' name would otherwise imply a write. It also discloses the downstream flow (user reviews, adds photos, posts, free for buyers), though it says nothing about link lifetime or reuse, which the idempotentHint implies but never explains.

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 sentences, no filler. The core action is front-loaded and the no-posting constraint plus the user's follow-up steps follow immediately in the same compact span.

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?

With no output schema, the description usefully implies the return value is a link the user opens. For a five-parameter, non-mutating tool that is largely sufficient, though it could say what a caller should do with the returned link and whether re-calling produces the same link.

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 80%, so the schema already documents category, deadline, budget and description. The description adds no field-level guidance, not even which fields are required or how free-text description maps to the brief; it only restates that the input is a description of the wanted item.

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 names a specific verb and resource: turning a user's description into a pre-filled job post link on The Spool List. Crucially it clarifies that nothing is posted, which distinguishes it from any sibling that might create or browse actual jobs.

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 usage context is clear — the user wants something custom-made and will review and post the brief themselves. However, no sibling is named and no exclusion or alternative (e.g. estimate_job_cost for pricing-only questions, browse_open_jobs for existing listings) is stated, leaving routing to inference.

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