get_profiles_posted_jobs

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

With no annotations, the description must disclose behavioral traits. It does not mention authentication requirements, rate limits, or what constitutes a 'posted job' (e.g., does it include reposts or only original job posts?). The return format is also unspecified.

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 extremely concise at one sentence with no unnecessary words. It is front-loaded and efficient.

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?

Given no output schema, 36 sibling tools, and potential ambiguity (what are 'posted jobs'?), the description is insufficient. It lacks details on how to use the username parameter correctly, what the response looks like, and how this tool differs from other job-related tools (e.g., 'get_company_jobs', 'search_jobs').

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 parameter 'username' is described in the schema as 'LinkedIn job id', which is contradictory and misleading. The description fails to clarify this inconsistency, leaving the agent confused about whether to provide a username or a job ID. Since schema coverage is 100% but the schema description is incorrect, the description should compensate but does not.

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 'Get profile's posted jobs' clearly states the action (Get) and the resource (profile's posted jobs). It distinguishes from sibling tools like 'get_profiles_posts' (which likely returns all posts) and job-specific tools like 'get_company_jobs' (company-centric).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'get_profiles_posts', 'get_job_details'). There is no context on prerequisites, such as requiring a LinkedIn profile username, or when to choose this over other job retrieval tools.

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