bind_virtuals_tender_job

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

Annotations already declare that this is an idempotent, non-destructive mutation in an open-world context. The description adds useful behavior beyond that: FarmDash independently verifies the Base client, provider, and evaluator before binding, and the call requires an authenticated session. It still does not explain failure handling or exactly what state changes on binding.

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 description is compact and front-loads capability and auth context before the core action. The bracketed metadata is dense but relevant; overall there is little wasted text.

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 mutation with six required identity/auth parameters, no parameter descriptions, and no output schema, the description is too thin. It covers prerequisites, auth tier, and verification behavior, but omits parameter meaning, return behavior, and what happens when verification fails.

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% across six required parameters. The description only loosely explains 'onchainJobId' and 'role' via 'on-chain ACP job ID' and 'committed role'; it says nothing about sessionId, sessionToken, agentAddress, or tenderId semantics beyond what the bare schema shows.

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 states a specific action and resource: 'Report a customer-created on-chain ACP job ID for one committed role.' This distinguishes the binding step from sibling operations like prepare_virtuals_tender_v2, authorize_virtuals_tender_v2, and evaluate_virtuals_tender, though it does not explicitly name those 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?

The bracketed capability and tier metadata imply deployment prerequisites and an authenticated x402/subscription session, and 'committed role' hints at timing. However, it does not explicitly say when to use this versus adjacent tender tools such as authorize, evaluate, or hire.

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