hires_list_applications

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

With no annotations provided, the description carries the burden of behavioral disclosure. It notes that the tool lists applications across 'all accessible jobs' and supports filtering, but it doesn't mention pagination behavior, default sorting, or response structure. The absence of any warning about side effects is appropriate for a read-only endpoint, but deeper details are left to the schema.

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 two sentences with the core action front-loaded and no redundant phrasing. Every clause adds value: scope, filter capabilities, and use cases.

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?

For a tool with 13 optional parameters and no output schema, the description gives a clear high-level overview and practical use cases, but it does not mention the include parameter for embedding relations or pagination defaults. The schema fills most gaps, and the description is sufficient for an agent to decide when to use it, though not exhaustive.

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 schema already provides descriptions for all 13 parameters (100% coverage), so the baseline is 3. The description adds a compact summary of filter dimensions ('candidate, job, stage, status, AI score range, and date ranges'), which helps the agent quickly map natural-language requests to parameter groups. This elevates it above baseline.

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 opens with 'List applications across all accessible jobs,' which provides a specific verb (list), resource (applications), and scope (all accessible jobs). This clearly distinguishes it from sibling tools like hires_get_application (single application) and mutation tools like hires_create_application.

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?

It explicitly states 'Use for pipeline analytics, sync jobs, and ATS dashboards,' giving concrete contexts for when to invoke this tool. It doesn't mention alternatives or exclusions, but the use cases are clear enough to guide selection.

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