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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation. The description adds genuinely useful context beyond that: the job is non-custodial and must be funded via a separate step, which tells the agent the create call moves no money. It omits what happens on duplicate submissions, what identifier is returned, and any permission requirements.

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?

Three short sentences, front-loaded with the action and followed by the environment constraint and the funding caveat. The trailing "No partnership" fragment is terse to the point of ambiguity, but overall there is little waste.

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 an 11-parameter, 5-required financial job-creation mutation with no output schema and no annotations covering money movement, the description is thin. It never says what a created job looks like or returns, how it relates to the dry-run sibling, or how budget/perProofAmount/maxProofs interact to define the escrow.

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 55% and 11 parameters are present; the description only restates the asset/chainId pairing that the schema already documents for those two fields. Required parameters budget, perProofAmount, and maxProofs have no description anywhere, and optional fields like perKOLCap, requiredLink, deadlineHours, requiredTicker, and minPostAgeHours are untouched, so the description does not compensate for the coverage 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 specific verb and resource ("Persist a campaign or content job") and the title names it as a create operation. It does not differentiate from the close sibling crew_job_create_dry_run, nor explain that the schema's `type` enum extends beyond campaign/content (design, research, community, feedback), so the scope is slightly narrower than the actual tool.

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?

"Use chainId=flop-devnet and asset=FLOP for the community flop-htlc rail" gives a concrete usage context, and "fund separately" implies a follow-up with crew_job_fund. But there is no explicit when-to-use vs. the dry-run sibling or crew_launch, and no stated prerequisites (wallet, auth, prior discovery of KOLs).

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