jobs_workday_board

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

No annotations provided, so description carries full burden. It reveals the tool is credential-free and returns public ATS JSON, but does not disclose rate limits, error handling, or empty result behavior. Adequate but limited.

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?

Four compact sentences with no wasted words. The main purpose is stated first, followed by essential details about paging and parameter sources.

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?

Covers purpose, paging, parameter sourcing, and public nature. Lacks description of the return format beyond 'public ATS JSON', which could be improved. Without an output schema, the agent would benefit from knowing the structure of a job posting item.

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 coverage is 100%, but the description adds meaningful context by explaining how tenant, datacenter, and site map to the careers URL and providing an example. This goes beyond the schema's individual parameter 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?

Clearly states it lists a Workday tenant's job board, specifies public Workday (CXS) postings, and mentions paging via limit/offset. Distinguishes itself from sibling tools like jobs_workday_job by focusing on board-level listing.

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?

Provides clear context: the tool lists public postings and requires tenant, datacenter, and site from the careers URL. Does not explicitly state when not to use it or list alternatives, but the purpose is sufficiently specific.

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