panelica_git_get_v1_git_repositories_id_pipelines

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description's 'Read-only' line mostly restates those. It does add a useful authorization precondition, 'Required scopes: git:read', which is beyond the annotations. There is no mention of pagination, filtering, or response shape, so the behavioral context is adequate but not rich.

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 compact and front-loaded, with the action 'List pipelines' first, followed by the endpoint, category, scope, and safety note. There is no filler or redundant explanation beyond the harmless repetition of 'Read-only.' It is appropriately sized for a simple GET list endpoint.

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?

All essential invocation details are present: HTTP method, path, required repository id, and required scope. The annotations cover the read-only and idempotent behavior, so the absence of an output schema is not critical for such a simple list operation. It could add pagination or response-shape hints, but the core contract is complete enough for an agent to call it correctly.

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 schema only describes the single parameter as 'Path parameter: id', which is low-value on its own. The description's full endpoint path, '/v1/git/repositories/:id/pipelines', clarifies that 'id' is the Git repository identifier, adding real semantic meaning beyond the schema. With 100% schema coverage and one required parameter, the agent has enough to invoke the tool correctly.

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 opens with 'List pipelines' and includes the exact HTTP path 'GET /v1/git/repositories/:id/pipelines', making the verb, resource, and repository scope clear. It is distinguishable from sibling git endpoints (branches, commits, webhooks, stats) because it names pipelines as the resource. It stops short of a 5 because it never explains what a pipeline is or explicitly contrasts itself with any sibling.

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 gives no guidance on when to use this tool instead of related pipeline tools such as creating, updating, or deleting a pipeline. It only states the HTTP method, required scope, and read-only nature, which imply retrieval but do not provide explicit use cases, exclusions, or alternatives.

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