evaluate_virtuals_tender

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

Annotations already disclose destructive=true, idempotent=true, and openWorld=true. The description adds auth context ('x402_or_subscription_with_authenticated_session'), deployment prerequisites, and the evaluator-identity constraint, but does not explain what state changes on complete/reject or what errors/results look like.

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 short, but the bracketed metadata header is dense and comes before the actual action sentence, so the useful purpose statement is not front-loaded. Every part does carry information, but it reads as machine metadata rather than agent-facing prose.

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 destructive, authenticated, four-required-parameter mutation with no output schema and no parameter descriptions, the definition says too little. It omits what evaluation does operationally and leaves all parameter semantics to the schema.

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 four required parameters. The description names none of them and provides no guidance on tenderId format, sessionToken, agentAddress, or sessionId, so callers must infer all parameter meaning from names and regex patterns alone.

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: 'Request evaluation or resume settlement for a fully bound customer-funded ACP tender.' It is distinguishable from siblings like bind_virtuals_tender_job or cancel_virtuals_tender, though the ACP/tender jargon reduces immediate clarity.

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?

'FarmDash can only complete/reject jobs committed to its evaluator identity' is a useful precondition, and the capability gate is noted. However, there is no explicit guidance on when to choose this over get_virtuals_tender, cancel_virtuals_tender, or when 'evaluation' vs 'resume settlement' applies.

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