lax submit

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

Annotations already flag openWorldHint=true and idempotentHint=false, and the description adds real context beyond them: it writes external data, transmits contact and payout address (sensitive disclosure), requires owner approval before calling, and warns that acceptance is not a payout guarantee. That is the exact set of side effects and risk semantics an agent needs before an irreversible external write.

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 action is front-loaded in the first sentence, followed by risk and precondition. The five-item negation list is somewhat long but each item rules out a plausible confusion with a neighboring operation, so little is wasted.

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?

Authorization, data disclosure, and payout caveats are well covered for a seven-parameter external write with annotations. However, with zero schema description coverage and no output schema, the absence of any parameter-level guidance leaves a meaningful gap for an agent assembling the payload.

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 0%, so all seven parameters carry no documentation anywhere, and the description only names 'contact' and 'payout address' in passing. Nothing explains job_id, builder, repo_or_patch_url, agent_did, or notes, so the description largely fails to 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 ('Send a work submission to the LAX organizer') and immediately bounds the operation with a list of things it does not do. It does not name the sibling tools directly, but the negations (no offer registration, no bidding, no PACT acceptance) let an agent separate it from the get/list/search siblings.

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?

Gives an explicit precondition ('Call only after the owner approves the exact submission') plus a clear negative scope listing adjacent actions this tool does not perform. It stops short of naming an alternative tool to use for those excluded actions, so the routing is implied rather than spelled out.

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