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

With no annotations, the description carries the full burden and discloses meaningful behavioral traits: return fields, the needs_fixtures waiting state, that a new pot takes no money until example answers are added, and the transition to pot_waiting and then an open pledge URL. It still does not cover permissions, idempotency, or error behavior, but it provides strong lifecycle context.

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 front-loaded with the core action, then efficiently adds return values, waiting-state behavior, and open-state behavior. Every sentence contributes distinct information without redundancy.

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 exists, and the description partially compensates by naming return fields and lifecycle states. However, with no annotations, incomplete parameter coverage, and no sibling routing, it remains incomplete for reliable invocation in a crowded toolset.

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 only 50%, with request_id having no description and requester_key documented in the schema. The tool description adds no parameter-level meaning, such as what request_id refers to or how requester_key is used, so it fails to compensate for the 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?

The description states a specific action: create or return the bounty pot for a queued request. It clarifies the underlying operation despite the tool name 'request_escalate' not being explicitly defined. It does not distinguish this tool from siblings like bounty_post, bounty_pledge, or bounty_pot_contract.

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 phrase 'for a queued request' implies when the tool is relevant, and it points to bounty_pot_contract as the next step. However, it gives no explicit when-to-use guidance, no when-not-to-use conditions, and no direct comparison to alternative tools.

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