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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses critical traits: no salary field, one page of up to 20 jobs, a $0.002 USDC charge per successful call, x402 payment options, and no charge for failed calls. This is exactly the kind of operational context an agent needs before invoking a paid API.

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?

The description is a compact, front-loaded block: source and scope first, then field availability, pagination behavior, and pricing. Every sentence carries operational information, with no filler.

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?

Given the presence of an output schema, read-only/open-world annotations, and a fully documented single parameter, the description covers the remaining unknowns: dataset scope, absence of salary data, page size, and payment terms. Nothing essential for correct invocation is missing.

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% and the single `page` parameter is already documented in the schema. The description still adds useful meaning by explaining that each page contains up to 20 jobs, clarifying the practical effect of the pagination parameter.

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 exactly what the tool returns: job listings from The Muse public API, with named fields and a US/remote scope. It clearly identifies the source, though it does not explicitly contrast itself with the many sibling job-board tools.

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?

The source-specific name and description imply that this tool is for retrieving The Muse job listings. However, it gives no explicit guidance on when to choose it over the dozens of other job-board tools, nor any exclusions or prerequisites.

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