search_jobs

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

With no annotations, the description carries the burden and does well: it discloses that the user's account is never involved, warns about IP rate-limiting, and gives a retry wait. It doesn't cover every operational detail, but the key caveats are present.

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?

Three compact sentences, each serving a distinct purpose: purpose/auth, parameter usage, and rate-limit/next-step guidance. No filler or redundancy.

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 9-parameter tool with no annotations, the description covers the non-obvious operational aspects (no auth needed, rate limits, follow-up via get_job). Some filter parameters are not explicitly discussed, but the output schema and enum values fill most gaps.

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 description coverage is 0%, so the description must compensate. It explains location with concrete examples, suggests a workplace='remote' combination, and documents limit max 50. Other parameters rely on their titles and enums in 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?

States a specific verb and resource: 'Search LinkedIn job postings'. It also clarifies 'no login required' and directs to get_job for full descriptions, distinguishing it from auth-related and job-detail siblings.

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?

Explicitly tells the agent to use get_job with a result's job_id for the full description, and provides practical guidance on location free text, combining with workplace='remote', and handling rate-limit errors with a wait-and-retry strategy.

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