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

The annotations already declare non-read-only, non-idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: every call is metered (units consumed) and produces a 'signed tick', signaling a billed, accountable side effect tied to the offer's network. It does not clarify whether units are charged on failure or whether ops are retryable despite non-idempotency, which keeps it below a 5.

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?

Two tightly packed sentences with the core action front-loaded and the return/metering note immediately after. Some phrasing ('signed tick', 'per the offer's network') is jargon-dense, but nothing is redundant.

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?

Return behavior is covered inline ('result + metered units') and no output schema exists, so that gap is closed. However, with 0% schema coverage and an opaque free-form 'params' object, an agent still lacks enough per-parameter guidance to construct a correct op payload.

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%, so the description carries the full burden. It only adds meaning for 'op' by listing candidate values (store/fetch/infer/connect/job); 'sessionId' and the open-ended 'params' object remain entirely undocumented, leaving two of three parameters unexplained anywhere.

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 names a specific verb and resource ('Execute one op inside an open resource session') and enumerates the op families (store/fetch/infer/connect/job), which lets an agent distinguish this from session lifecycle siblings like wide_request or wide_request_close. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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?

'inside an open resource session' implies the prerequisite that a session must already exist, and the op list hints at the range of valid usage, but the tool never states when to pick this versus wide_request, wide_request_status, or wide_request_tick_verdict. Usage is implied rather than instructed.

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