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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds materially beyond that: pricing ($0.002 USDC per successful call), payment rails (x402 on Base, Solana or Arc), and the notable fact that failed calls are not charged — all decision-relevant for an agent.

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?

Front-loads identity and source, then usage, then cost — a sensible order. The field enumeration is somewhat long, but every element maps to an actual output field, so little is wasted.

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 an output schema present, the description needn't explain return values, and it covers inputs, cost, and payment mechanics. The only omission is any note on result limits or pagination behavior, which for a multi-result listing tool an agent would want to know.

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 each parameter is described there, so the schema carries the semantics. The description only restates the filters generically ('optional keyword and remote-only filters') and adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 ('Open positions of a company that hires through Breezy HR') plus the exact data source (public career-site feed), and enumerates returned fields. Naming Breezy HR as the platform is precisely what separates it from 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?

Explains how to supply the required identifier ('Give the company's Breezy subdomain — the part before .breezy.hr') and mentions the optional keyword and remote-only filters. It does not explicitly say when to prefer this over sibling boards, though the platform-specificity makes the choice fairly evident.

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