realtime_glassdoor_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether operations are read-only, any authentication needs, rate limits, or response formats. The tool name implies real-time data, but the description adds no behavioral context beyond the operation list.

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 as a concise bullet-like list of operations with their required params. It is front-loaded with a clear overview and avoids unnecessary prose. Every line contributes useful information.

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?

The description covers all 9 operations and their required parameters, which is sufficient for basic invocation. However, it lacks details about return values, optional parameters, pagination, or any operation-specific nuances. Given the tool has no output schema and 9 distinct operations, more context would be needed for a complete understanding.

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's 'args' is a generic object with no per-operation properties, making the description the authoritative source for parameter requirements. It explicitly lists each operation's required parameters (e.g., company_salaries requires company_id and job_title), providing essential semantics that the schema lacks.

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 resource (Glassdoor) and lists the specific data types (company search, overview, reviews, salaries, interviews, jobs) and operations. It distinguishes from siblings by being Glassdoor-specific, though it lacks an explicit verb like 'search' or 'retrieve' in the opening sentence.

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 no guidance on when to use this tool versus alternatives (e.g., jsearch, job_salary_data) or when not to use it. It simply lists operations without contextual recommendations.

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