job_stats

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

With no annotations, the description itself must communicate behavioral traits. 'Counts' implies a read-only aggregation rather than a mutation, but the description adds no detail about scope, freshness, permissions, or whether the counts are computed on demand.

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?

A single, front-loaded sentence with no filler. Every phrase contributes meaning, naming the resources counted and the grouping dimensions.

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 zero-parameter stats tool with an output schema present, the description is nearly complete. It could add a phrase about what 'pipeline' refers to or whether these are current counts, but the basics are covered.

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 tool has zero parameters, so the baseline is 4. The description adds meaningful grouping semantics (status/fit) beyond the empty schema, making invocation expectations clear.

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 indicates this tool returns counts of jobs and applications aggregated by status, and jobs also by fit. This distinguishes it from list/detail siblings, though it omits an explicit verb like 'retrieve' or 'get'.

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?

No guidance is given about when to choose this tool over alternatives such as list_jobs, job_detail, or list_applications. The 'counts' wording implies an aggregate use case, but the description never states this directly or names any sibling as an alternative.

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