get_pipeline

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

With no annotations, the description carries the full burden of explaining behavior. It discloses that the output is grouped by status, but it does not mention any other behavioral traits such as whether the result is a summary, list, or counts, nor does it describe pagination or ordering. The description is adequate for a simple read-only tool but lacks enriching detail.

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, focused sentence with no filler or redundancy. It front-loads the action and object, making it easy to parse and understand at a glance.

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's low complexity (no parameters, no output schema) and clear purpose, the description is minimally adequate but not fully complete. It does not explain what the 'pipeline' consists of (e.g., job names, counts, stages) or what the output shape looks like, leaving some ambiguity about the exact return content.

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 correctly implies no inputs are needed. Since there are no parameters to explain, the description does not need to add parameter semantics beyond what the schema already communicates (empty schema).

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 shows the job application pipeline grouped by status. It uses a specific verb ('Show') and resource ('your job application pipeline') with an explicit grouping dimension, making it distinct from sibling tools like fetch_jobs or search_jobs.

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 implies usage for viewing an overview of application statuses, but it lacks explicit when-to-use guidance or exclusion criteria relative to sibling tools. There is no mention of alternatives or conditions, so the agent must infer context from the tool's purpose.

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