Get stale jobs

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does specify the filtering logic (statuses and date threshold) and states the default of 14 days computed against today. However, it does not explicitly state that this is a read-only operation or describe side effects, permissions, or return format. The 'List' verb implies safety, but the absence of annotations makes this a moderate, not strong, disclosure.

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 a single, compact sentence that front-loads the core functionality and includes essential details (statuses, threshold, default, baseline date). No wasted words.

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 the simple single-parameter schema and lack of output schema, the description adequately explains what the tool does and the input behavior. It does not detail return shape or ordering, but these are not critical for this simple list operation. It is complete enough for an agent to understand the tool's role.

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 only parameter, 'days', has a clear schema description covering its meaning and default. The tool description adds no new parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 tool lists applications filtered by specific statuses ('Awaiting Response' or 'Applied') and by a date threshold. This is a specific verb+resource+scope description that distinguishes it from sibling tools like list_jobs or get_job.

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 on when to use the tool: when needing to surface applications stuck in certain statuses older than a configurable number of days. It does not explicitly name alternatives or exclusions, but the criteria are well-defined enough for an agent to select it appropriately.

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