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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful fact that the response includes the full job description and depends on a shortcode sourced elsewhere, but says nothing about auth, rate limits, or error behavior when the shortcode is invalid. Adequate but not rich.

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 sentences, front-loaded with the primary action, zero filler. The alternative-routing guidance is packed into the second sentence efficiently.

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?

An output schema exists, so return-value details are correctly omitted, and both parameters are documented in the schema. The dependency chain (shortcode must come from the board tool) is explained, though the description could note the company slug's role more directly. Nearly complete for a two-parameter detail fetch.

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 both parameters (id as shortcode, company as account slug) are already documented. The description reinforces that id is a 'posting shortcode' but adds no syntax, format, or sourcing detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (Fetch), resource (one Workable job-posting response), and scope (with its full description, by posting shortcode). It is clearly distinguished from the plural sibling jobs_workable_postings, so an agent can tell the two apart without opening either 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?

Explicitly names the alternative (jobs_workable_postings) and the condition that selects it (browse the board and obtain the shortcode). The routing between the two tools is fully spelled out with nothing left to inference.

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