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

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false). The description goes beyond that by disclosing the funding requirement and the concrete rehire side effects: a task.rehire_offer event, a preferred-flagged bid, and auto-award eligibility/within-budget rules. Idempotency and failure modes for the base repost path are not covered.

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?

Front-loaded with the core action, then the override list, then rehire mechanics, then the funding prerequisite. The parameter enumeration is dense but each clause carries information; no filler sentences.

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 10-parameter write tool with nested budget object, low schema coverage and no output schema, the description covers the essential model: copy the source spec, override selectively, and the rehire variant's behavior. Remaining gaps (budget constraints, bidding window/deadline semantics, result shape) are minor but non-zero given the tool's 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 description coverage is only 30%, so the description must carry weight, and it enumerates the overridable fields (input_payload, title, description, budget, deadline, bidding_window_seconds, auto_award) and explains the rehire/preferred_provider_id semantics beyond the schema. It does not clarify budget currency/amount format or what bidding_window_seconds or auto_award actually do when overridden.

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 (post/repost) and resource (one of your past tasks' spec as a new open task), and the 'past task' framing cleanly separates it from post_task (create from scratch) and post_enrichment_task. An agent can tell which sibling to pick without opening schemas.

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?

Makes clear the context for use (re-running an existing spec, optionally with overrides) and gives the rehire condition (a provider who already completed paid work) plus the prerequisite that posting needs a funded wallet. It stops short of explicitly naming when to prefer post_task instead, so it is clear context without exclusions.

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