submit_delegated_job

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

No annotations provided, so description carries full burden. Discloses that provider works first, pulls price from delegated allowance, and that delegate can pull without signature within cap. Explains behavior of max_price_lamports omission.

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?

Every sentence adds value: purpose, behavior, prerequisite, parameter nuance. No wasted words. Well-structured and front-loaded.

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?

No output schema, but description covers return behavior for price confirmation. Covers prerequisites and behavioral traits. Lacks details on success output for full submission, but may be inferred.

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 coverage is low (17%), so description should compensate. It explains max_price_lamports well (confirmation cap, omit for price check). Does not explain input, provider_npub, capability, kind_offset, timeout_secs. Some value added but incomplete.

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?

Description clearly states action (Submit), resource (job), and payment mechanism (delegated USDC). It distinguishes from siblings like submit_and_pay_job by emphasizing the delegation aspect.

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?

Explains prerequisite of active delegation and mentions checking with get_delegation. Includes scenario for omitting max_price_lamports. Lacks explicit when-not-to-use compared to alternatives.

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