List a company's open roles

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

With no annotations, the description must disclose behavioral traits. It mentions 'public postings' suggesting a safe read operation, but does not address pagination, authentication, rate limits, or response format beyond the implied list. This is insufficient for agents to anticipate side effects or limitations.

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 efficiently state the core function and key parameter guidance. No redundancy, with the most important information front-loaded.

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?

The description covers the main purpose and key parameters, but lacking an output schema, it does not specify the return format or pagination behavior. Optional parameters like query and minSeniority are only in the schema, and the description omits any mention of them, relying on the schema for their semantics.

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 description adds meaningful context beyond the schema by explaining 'provider' enum values and providing a concrete slug format example. It also clarifies that these are the two required parameters. Schema coverage is 75%, and the description fills the gap for the undocumented provider parameter.

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 'Fetch all public postings from a single company's ATS job board,' specifying the verb, resource, and scope. It distinguishes from sibling search_jobs by emphasizing 'single company' and listing supported providers.

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 provides clear context that this tool targets one company's ATS job board, implying when to use it (known company). However, it does not explicitly mention alternatives or when not to use it, such as for cross-company searches, which search_jobs likely handles.

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