jobs_workable_postings

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

The description discloses key behavioral traits: normalization to a shared shape, fetching detail per job via a single-posting endpoint, and being credential-free. It does not mention pagination, rate limits, or potential destructive actions, but given no annotations, it provides useful behavioral context beyond the bare minimum.

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 concise at 4 sentences, front-loading the core purpose, then explaining normalization, filters, company parameter, and detail fetching. Every sentence adds value without redundancy or unnecessary detail.

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, the description covers key aspects: input parameters, normalization, detail fetching, and credential-free access. However, it lacks mention of pagination or explicit differentiation from the singular 'jobs_workable_posting' sibling, which would improve completeness for a listing tool.

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?

With 100% schema coverage (baseline 3), the description adds meaningful context, especially for the 'company' parameter by explaining it is the Workable account slug from the careers URL. It also clarifies that filters are optional and groups them, adding value beyond the schema descriptions.

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 verb 'list' and the resource 'Workable postings', specifies normalization to a shared Job shape, and mentions optional filters. It effectively distinguishes this tool from siblings by targeting Workable specifically, which is evident from the sibling list containing other job board 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 Workable postings but does not explicitly guide when to use this tool over alternatives like 'jobs_workable_posting' (singular) or other job board tools. There is no mention of when not to use it or specific scenarios that favor other tools, leaving the agent with implied rather than explicit guidance.

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