glassdoor_listing: GET /

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

With no annotations, the description fully details the return structure (fields like title, company, salary estimate, etc.) and pagination behavior via nextPageToken. It does not mention any destructive actions or auth requirements, but for a GET endpoint this is acceptable.

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 composed of two clear paragraphs: one explaining functionality and one listing use cases. It is efficient without redundancy, though a bit verbose for an experienced user.

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 tool has no output schema and 5 parameters, the description covers the return values (array of jobs with specific fields) and pagination, plus use cases. It lacks details on default sort or domain, but overall it is complete enough for an agent to use correctly.

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?

The input schema has 100% parameter description coverage, so the description only adds minimal context (like 'searches by keyword and location with sort, domain targeting'). The baseline of 3 is appropriate as the schema already explains each parameter well.

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 clearly identifies the tool as retrieving GlassDoor job listings, specifying search by keyword and location with optional sort, domain, and pagination. It distinguishes itself from its sibling 'hasdata_glassdoor_job_getJobDetails' by stating it returns listings for downstream scraping.

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 description provides explicit use cases like building job feeds and monitoring trends, and mentions the alternative endpoint for full details. However, it does not explicitly state when not to use this tool (e.g., if full details are needed immediately).

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