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

Adds real behavior beyond the annotations: the pipeline file is read at connect time, the result is reported back as 'definition', the required permission is pipelines.manage, and re-connecting an already-connected repo is refused with its id (consistent with idempotentHint=false). It doesn't describe what else gets created or whether the connection can be partially rolled back, which keeps it at a 4.

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?

Front-loaded with the effect, then the caveats and the permission requirement, with no filler sentences. The phrasing is telegraphic in places ('refused with its id', 'Needs pipelines.manage'), which is efficient but slightly clipped.

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 an 8-parameter mutation tool with no output schema, the description covers the essential unknowns: permission requirement, duplicate behavior, the side effect of starting runs, and the workspaces_only escape hatch. Only the shape of the returned definition and error surfaced on duplicate are left implicit.

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 description coverage is 100%, so the baseline is 3. The description adds a little meaning for workspaces_only ('Ankra Workspaces alone, with no runs') and the connect-time read of the pipeline file, but leaves provider, cluster_id, application_id, default_branch and credential_name entirely to the 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?

States a specific verb and resource ('Connect a repository to Ankra Pipelines') and immediately scopes it: it makes pushes, PRs, tags, schedules and merge train events start runs from a committed .ankra/pipeline.yaml. That clearly separates it from the adjacent connect_gitops_repository sibling, which targets a different subsystem.

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?

Gives clear context for calling it (you want pipeline runs triggered by SCM events) plus two concrete conditions: an already-connected repo is refused, and workspaces_only is the no-runs variant. It does not explicitly say when to prefer connect_gitops_repository or disconnect_pipeline_repository instead, so it stops short of a full when/when-not routing rule.

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