list_hiring_pipeline_stages

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It states the returned structure ({id, label}) and suitability for filtering, but does not explicitly mention idempotency or that it is a read-only operation. However, 'list' implies read, and the simplicity of the tool makes this sufficient.

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 with no wasted words: first states the core action, second provides a usage tip and return purpose. Information is front-loaded and efficiently delivered.

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 tool has an output schema, the description need not detail return values. It covers purpose, parameter usage, and output utility. The only minor gap is not explicitly stating that it is a read-only operation, but overall it is complete for a simple list tool.

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 input schema has 0% description coverage, so the description must compensate. It adds meaning by specifying that pipeline_id=0 corresponds to the master pipeline, providing context beyond the schema's type and required flag. It does not explain other possible values, but this is acceptable given the tool's focused use.

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 hiring pipeline stages for a given pipeline, with a specific verb ('list') and resource ('hiring pipeline stages'). It also distinguishes from sibling tool 'list_hiring_pipelines' by focusing on stages rather than pipelines themselves.

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 explicitly advises using pipeline_id=0 for the master hiring pipeline, indicating when to use this tool. It also implies its utility for filtering assigned candidates by hiring stage, providing clear context without needing to specify exclusions.

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