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

Goes well beyond the supplied annotations: it discloses the coding_jobs_enabled gating flag, notes that it is separate from barter_broker_enabled, and names the CODEJOBS_OFF sentinel returned while the flag is off. It also sets expectations that scoping is non-binding and that pricing scales with tier, which an agent cannot infer from readOnlyHint=false/openWorldHint=true.

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-loads purpose, then WHEN, then behavioral caveats, then the gating behavior and an example — a sensible ordering with little wasted text. The gating sentences are slightly dense and somewhat separable from the core scoping purpose, but each still carries information an agent needs.

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 still tells the agent what comes back (a suggested tier plus pay/barter/free term options) and the failure mode (CODEJOBS_OFF). Combined with zero required parameters and full schema coverage, an agent has everything needed to call it correctly and interpret the result.

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 key, brief, title, and tier_hint are already documented, and the description mostly restates the flow rather than each field. It adds only marginal meaning beyond the schema ('longer/harder costs more' for tier choice) and the example call `barter_code_scope {}` confirms all inputs are optional, which is baseline-level value here.

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 ('Scope a coding job') and immediately situates it in the code-job pipeline: the broker proposes a tier and three term options, but terms stay TBD until Perry or Rock accepts. That clearly separates it from barter_code_accept, barter_code_offer, and barter_code_status, which act on a job after scoping.

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?

Explicit 'WHEN: you want Dead Brands (Perry or Rock) to write code' gives a concrete trigger condition, and the 'nothing is guaranteed at scoping / terms TBD until accepted' line implies when to move on to the offer/accept tools. It stops short of naming those siblings or stating exclusions (e.g. when not to scope), so it is strong but not fully exhaustive.

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