indeed_scraper

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

No annotations are provided, so the description carries the burden. It discloses the credit cost, the special summary object at the end, and the input format. However, it does not mention potential issues like scraping rate limits, error handling, or the fact that Indeed might block requests, which would be useful 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?

The description is well-structured with clear sections, front-loading the main purpose, then credits, notes, and return format. It is slightly verbose in the returns section, repeating some field names, but overall efficient.

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?

Despite lacking an output schema, the description fully specifies the return structure including the array of job objects and the trailing summary object. It covers input requirements, credit cost, and output format, leaving no major gaps for an AI agent.

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% with a single 'url' parameter. The description adds value by explaining the URL must be a complete Indeed search-results URL and how to construct it, going beyond the schema's basic description.

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?

The description uses a specific verb ('Extract job listings') and resource ('Indeed search results URL'), and lists the structured fields returned. It distinguishes itself from sibling scrapers by naming Indeed explicitly and detailing the URL input format.

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?

Provides clear guidance on building the input URL via Indeed's search UI and notes that it requires a complete search-results URL rather than discrete parameters. Lacks explicit when-not-to-use scenarios or comparisons with other job scrapers, but the context is sufficient.

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