Get the pipeline feed

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

Annotations already indicate the operation is read-only, idempotent, and non-destructive. The description adds meaningful context beyond those annotations by specifying authentication scope, repository visibility, ordering ('newest first'), and that it returns only the latest pipeline per repository.

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 deliver the full meaning without wasted words. The key scoping factors — account feed, visible repositories, latest pipeline, newest first, and the one-request advantage over list_pipelines — are all front-loaded and succinct.

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?

With no parameters and a present output schema, the description covers everything an agent needs to know: what the feed contains, its scope, its ordering, and how it compares to the related list_pipelines tool. The annotations complete the safety picture.

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 takes zero parameters, so the description has no parameter burden to carry. The baseline of 4 applies here, and the description does not conflict with the 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 identifies the resource (the activity feed of the authenticated account) and the action (returns the latest pipeline of every visible repository, newest first). It also distinguishes itself from list_pipelines by presenting this as the 'state of everything' call, making its purpose unmistakable.

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 tells the agent when to use this tool: when it wants the overall state of all repositories in a single request. It also names the alternative (list_pipelines per repository) and explains that this tool replaces that multi-call pattern, giving clear selection guidance.

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