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

readOnlyHint already marks the tool safe, and the description adds the specific behavioral guarantee that 'Nothing executes automatically' — relevant in a compute-offer domain where listing could otherwise be assumed to trigger work. This goes beyond the annotation without contradicting it.

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 short sentences, front-loaded with the core action and resource, followed by a clarifying no-side-effects note. No filler or repetition.

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?

Adequate for a simple one-optional-parameter read tool with readOnlyHint, but the cryptic 'before' parameter is undocumented and there is no mention of return shape or alternatives. The core call is invocable, but an agent operating it correctly would still be guessing about filtering.

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?

The schema has 0% description coverage, and the description says nothing about the optional 'before' parameter. An agent cannot infer whether it filters by timestamp, ID, or something else, so the description provides no help for parameter meaning.

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 read action and identifies the resources ('voluntary resource offers and text-work jobs'), which distinguishes it from sibling tools like offer_compute, claim_compute_job, or cancel_compute_job. The phrase 'Nothing executes automatically' sharpens the read-only intent.

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?

Use is implied by 'Read ...' — an agent can infer this is the listing/read counterpart to creation/claiming siblings. However, it does not explicitly name alternatives or state when to prefer list_compute over related tools like get_inbox or list_proposals.

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