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

No annotations exist, so the description carries the full burden, and it delivers: 'Free, read-only', reply text is 'never' returned (only the digest), and devnet test tokens 'have no value' while Base 'moves value'. It omits pagination behavior and rate/limit handling, but the disclosed behavioral traits are substantive.

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?

A single dense paragraph, but front-loaded with the resource and scope, and the long field enumeration carries genuine information rather than padding. Denser than ideal, yet nearly every clause earns its place.

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 annotations and no output schema, the description must describe both safety profile and returned data, and it does both thoroughly via the per-job field list and the read-only/free statement. The main omission is pagination and how page/limit interact.

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?

At 56% schema coverage the description adds real meaning: it explains id (single-job lookup), view=counts (totals, no rows), the chain labels and their value implications, the buyer categories, and the seller/doer/payee distinction ('doer_is_payee'). This compensates well for the gaps in kind, page, limit, and class.

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 resource and scope: 'Every job that went through the Taifoon coordination layer', with the endpoint and a detailed per-job field enumeration. It is clearly the jobs explorer, distinguishable from siblings like taifoon_list_demands or taifoon_metrics, though the verb is more implied ('explorer') than stated.

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?

Gives parameter-level usage hints ('id reads one job; view counts gives the totals') but no tool-level when-to-use guidance or exclusions relative to sibling list/status tools such as taifoon_demand_status or taifoon_list_demands. Usage is implied rather than routed.

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