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

Goes well beyond the readOnlyHint annotation: it declares the tool only PROPOSES text and writes nothing, describes the returned artifacts (pipeline_yaml, notes, validation verdict), warns that unmappable third-party steps become failing stages rather than being dropped, and states the 20-file/256KB bounds. Rich, decision-relevant behavioral 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?

Front-loads the core purpose and remains information-dense with little waste. It is a single long paragraph though, and the edge-case behavior could be more scannable, keeping it short of a 5.

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 conversion tool with no output schema, the description covers inputs, required prerequisites, return shape, failure modes, limits, and the follow-up step for landing the change. An agent has everything needed 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?

Schema description coverage is 100%, so the schema already documents format inference, application_id resolution, and workflow_files semantics. The description adds the procedural note to read files first and pass their contents, but does not exceed the schema's parameter documentation, so baseline 3 applies.

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+resource (convert existing CI definitions into an Ankra pipeline) and enumerates the exact source formats it accepts. The scope is unmistakable and clearly distinguishable from the validate/propose siblings.

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 strong operational context: read files first with github_read_file/workspace_read_file, pass contents here, then land the result via scm_create_pull_request or github_create_pull_request. It doesn't explicitly contrast with cicd_propose_application_pipeline or the cicd_validate_* siblings, so the exclusion boundary is left implicit.

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