jobs.extract_indeed

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

No annotations are provided, so the description must carry the full burden. It states the tool extracts jobs and optionally saves to .txt, but lacks details on side effects (e.g., page modification), requirements (e.g., being on Indeed page), or what happens with no results. Insufficient for an agent to predict behavior.

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 very short but contains two ideas: extraction and optional saving. It is not overly verbose, but it lacks structure and important details. Could be more concise if it also provided essential context.

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 low schema coverage, no output schema, and no annotations, the description is incomplete. It does not specify the output format, behavior when limit is set, or how the extraction works. The tool seems simple but the description leaves many questions unanswered.

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 description coverage is 0%, so the description should compensate. The 'saveDir' parameter is hinted by 'Optionally save each job to a .txt file', but 'limit' is not explained at all. The description adds minimal meaning beyond the schema.

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' and identifies the resource as 'Indeed search results page', which clearly states the tool's function. However, it does not explicitly differentiate from sibling tools like 'jobs.indeed_next_page', but the purpose is still clear.

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 guidance on when to use this tool versus other extraction or job-related tools. The optional saving is mentioned but no context on prerequisites or exclusion criteria.

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