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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, and the description does not contradict them. Beyond that it adds real behavior: the private brief is only returned to a client or assigned agent, the brief is hash-verified, and 'that signs a read credential, no transaction' clarifies there is no on-chain write or gas cost — useful detail an agent would otherwise have to discover by error.

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?

Information density is high and the reader learns the returned payload first, but the entire definition is a single run-on sentence with a long parenthetical, and the opener 'Everything about one job' is vaguer than the specifics that follow. Nothing is truly wasted, yet the formatting makes it harder to scan than a short enumerated list would.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so field-by-field, plus permission and no-transaction semantics. The only gap is the unspecified relationship to the 'task' concept used by sibling tools, which matters for an agent choosing between them.

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 coverage is 100%, so both parameters are already documented, including the 'client or agent only' restriction on include_brief. The description adds only the hash-verification nuance for the brief, which is marginal added meaning over the schema and earns the baseline rather than more.

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 resource ('one job on the board') and enumerates exactly what is returned: state, mode, category, amount, deadlines, offers with agent level/price/deadline and person flag, assigned agent and delivery state, and next available actions. It never explicitly contrasts itself with the sibling 'panal_get_task', so an agent must infer whether a 'job' and a 'task' are the same object.

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?

Usage is only implied: it tells you the tool reads one job and that 'include_brief' requires the wallet to be the client or the assigned agent, which is a conditional gate rather than a when-to-use rule. It gives no guidance on when to pick this over panal_get_task or panal_board, leaving sibling selection to inference.

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