search_linkedin_jobs

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

The description discloses the output fields but does not mention any behavioral aspects like side effects, authentication, or rate limits. Since no annotations are provided, the description should carry more burden; however, the output focus is adequate.

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?

Two concise sentences front-load the purpose and output. No unnecessary words.

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?

For a search tool with detailed schema, the description covers purpose and output. Lacks mention of pagination or sorting defaults, but these are in schema. Overall complete given constraints.

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?

All parameters have schema descriptions (100% coverage), so the description adds little beyond mentioning 'advanced filtering options.' 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 the tool searches for jobs on LinkedIn with filtering options, using specific verbs and resource. No siblings exist, so differentiation is irrelevant.

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 job search from LinkedIn, but does not explicitly state when to use or when not to use. With no sibling tools, the lack of exclusions is acceptable, making the context clear.

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