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

Annotations cover read-only and open-world, but the description adds genuinely useful context beyond them: pricing at $0.002 USDC per successful call via x402, failed calls not charged, and the 25-per-page volume. It could go further on pagination behavior or rate limits, but the cost model is a strong disclosure.

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 sentence that front-loads the resource and source, then the returned fields, then the pricing. It is run-on but every clause (including cost and page size) is decision-relevant.

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 doesn't need to enumerate return fields but does so helpfully; the pricing/payment mechanism is the key missing-context item and it is covered. The main gap is lack of sibling differentiation for a crowded tool category.

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 already documents both params (search as job title/skill, page 1-20 default 1). The description restates the search term and page volume but adds no syntax or format detail the schema lacks, so 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 resource and scope: tech/startup jobs from Built In for a search term, with the fields returned and 25-per-page volume. The source ('Built In's public job search page') implicitly distinguishes it from sibling job boards, though no sibling is named explicitly.

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?

There is no when-to-use guidance despite dozens of sibling job-board tools (dice, indeed, linkedin_jobs, wellfound_jobs, etc.). An agent gets no signal about when Built In is preferable to alternatives, nor any exclusions.

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