company_job_salary

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

With no annotations, the description must carry the burden. The word 'Get' and 'estimated' indicate a read-only, approximate nature, but the description does not disclose data sources, potential inaccuracies, or behavior when no data is found. It suffices for a simple lookup but lacks deeper behavioral context.

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, front-loaded sentence that clearly states the tool's purpose with no redundancy or filler. Every word earns its place.

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 tool has 5 parameters and no output schema. The description gives a clear overview of the core functionality, but it does not explain the return format (e.g., salary range, currency) or explicitly differentiate between this tool and the sibling 'job_salary', leaving some ambiguity for an agent deciding between them.

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 schema provides full 100% coverage for all 5 parameters, so the baseline is 3. The description adds minimal value by naming job_title, location, and years_of_experience, but does not mention company or location_type, nor does it provide any syntax or format details 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?

Description uses the specific verb 'Get' and clarifies the resource as 'estimated job salaries/pay', scoped to 'a specific company' with optional location and experience. This clearly distinguishes it from the sibling tool 'job_salary' (which likely covers general salary data) and other job tools.

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 implies usage for company-specific salary queries by emphasizing 'in a specific company', but it does not explicitly state when to use this tool over job_salary or job_search, nor does it provide exclusions or alternative recommendations. The context is present but not fully developed.

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