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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial operational context: it uses the connected LinkedIn account, shares the protected Classic provider-search budget with people discovery, and requires honoring quota_protection and retry_after_seconds. These rate-limit and auth/budget details go well beyond the annotations.

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?

Front-loaded with the key disambiguation before getting into mechanics, and three sentences carry real information (scope, budget, quota). The final sentence is dense with two concepts but earns its place. Minor compression possible.

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 read-only search with no output schema, the description covers scope, return nature (postings, not people), and the quota/cooldown constraints an agent must respect. Adequate; a note on pagination or result shape would fully close the gap, but annotations and schema carry the rest.

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 100%, so all 9 parameters are already documented in the schema. The description references the filter dimensions (keywords, location, seniority, job type) but adds no format or default details beyond what the schema provides, so baseline 3 applies.

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+resource (search LinkedIn job postings) and immediately distinguishes it from the adjacent people-search tools by clarifying 'it returns job postings, not people.' An agent can place it relative to search_linkedin_people and get_job_posting_details without opening a schema.

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?

Gives a clear use case ('find companies that are hiring (a buying signal)') and an exclusion ('not people'), plus an operational rule against bypassing a people-search cooldown. It stops short of naming the sibling alternative (e.g. search_linkedin_people) explicitly, but the context is strong.

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