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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the description is not burdened with safety disclosure, yet it adds genuinely new behavioral facts: a per-call price of $0.002 USDC via x402 on Base/Solana/Arc and that failed calls are not charged. It also preempts a false expectation by noting the feed has no salary field. Only the absence of any note on rate limits or result freshness keeps it from 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?

Three tight sentences, front-loaded with what the tool returns, then the caveat, then the price. The enumerated field list is somewhat redundant given an output schema exists, which is the only waste.

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?

Source, returned fields, a known data gap (no salary), and the full payment model are all covered, and an output schema handles return-value detail. An agent has everything needed to decide to call it and to anticipate the billing behavior.

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% for the single parameter, with the range (1-50) and default (10) documented in the schema itself. The description adds nothing about limit, which is acceptable at full coverage but is the baseline rather than added value.

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 verb and resource ('Newest remote job postings from We Work Remotely's public RSS feed') and enumerates the fields returned, so the agent knows exactly what it gets. It does not, however, distinguish itself from the near-identical sibling jobs_we_work_remotely, leaving that ambiguity unresolved.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. This matters here because the sibling list contains both jobs_weworkremotely and jobs_we_work_remotely, and the description gives no basis for choosing between them or between this and the many other job-board tools.

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