List Hiring Pipelines

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context about MCP-side pagination and the fact that the underlying Recruit CRM endpoint returns all rows, explaining why pagination parameters exist. This goes beyond what annotations provide without contradicting them.

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, front-loaded with the verb and resource, and every clause adds information (pagination, return fields, use cases). No filler or redundant content.

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 low-complexity list tool with an output schema, the description fully captures purpose, return fields, and usage intent. It is complete enough for an agent to select and invoke this tool correctly without further documentation.

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?

Schema coverage is 100% with detailed descriptions for page and limit. The description reinforces the pagination context and links parameters to the tool's purpose (selecting pipelines/stages), adding a usage framing beyond the raw schema definitions.

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 uses a specific verb ('Lists') with a clear resource ('Recruit CRM hiring pipelines') and adds scope ('with MCP-side pagination'). It also states the returned fields and intended use ('selecting a job hiring pipeline or listing candidate hiring stages'), fully distinguishing it from siblings like list_candidate_hiring_stages.

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 indicates when to use the tool ('for selecting a job hiring pipeline or listing candidate hiring stages'), establishing clear context. It does not explicitly name alternatives or exclusion conditions, but the purpose-driven guidance is sufficient for this simple list tool.

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