glassdoor_listing: GET /

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

No annotations provided, so description carries full burden. It mentions returning array of jobs with fields and next page token, implying a read operation. However, it does not disclose rate limits, authentication requirements, or any destructive 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 a single paragraph of ~80 words. It front-loads the main purpose but includes a list of use cases that could be more concise. Not overly verbose, but could be trimmed.

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?

No output schema, but description lists returned fields (title, company, location, etc.) and next page token. However, it lacks details on response structure, error handling, or performance. Adequate but not comprehensive.

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 clear descriptions for all parameters. The description adds that domain is optional and nextPageToken enables pagination, but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 states it gets Glassdoor job listings by keyword and location with sorting, domain targeting, and pagination. It distinguishes from sibling tools like hasdata_glassdoor_job_getJobDetails (which is for full-detail 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 lists use cases (build job feeds, monitor trends, sourcing tools, downstream scraping) but does not explicitly state when not to use or compare with alternative listing tools like Indeed. No exclusion criteria.

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