post_job

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

No annotations are provided, so the description bears the full burden. It discloses the need to sign the payload but omits crucial behavioral traits such as whether the job submission is synchronous or asynchronous, what the response looks like, or how errors are handled. The agent is left uncertain about the invocation lifecycle.

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 sentences, 50 words, front-loaded with the core action. Each sentence contributes distinct value: purpose, usage context, and a prerequisite. No redundancy or fluff.

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 tool with 5 parameters (2 required) and no output schema, the description covers the prerequisite but lacks information about return value, error handling, or async behavior. While the schema covers all parameters, the agent may still need additional guidance to invoke correctly in a full workflow.

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?

Although schema coverage is 100%, the description adds meaningful context for key parameters: it explains the relationship between provider_id and the manifest, and why signature is required. This goes beyond the raw schema descriptions, though it does not elaborate on reward-related params.

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?

The description clearly states the action ('Submits a service request (job)') and the target ('to another agent'). It distinguishes this tool from siblings by specifying delegation of tasks defined in a provider's manifest, which is unique among the listed tools.

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?

The description tells agents to use this tool for 'delegating tasks defined in the provider's manifest' and provides a prerequisite ('sign the payload before posting'). It does not explicitly state when not to use it, but the context is clear enough for the given sibling list.

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