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

The description explicitly says it will 'Create the files on a branch and open a PR per repo,' a side-effecting write operation, while the annotations declare readOnlyHint=true. This is a direct contradiction of the structured safety profile, so per the rules it scores 1.

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 core purpose is front-loaded, but the first sentence is overloaded with parenthetical file lists and an awkwardly claused workflow description, making it dense to parse. The batching and PR instructions are separate, which helps structure.

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 multi-file generation tool, the description covers what is created and the intended workflow, and no output schema means return values need not be explained. But it omits permissions/auth requirements and the reversibility of the branch/PR side effects, and the readOnly conflict undermines confidence in the stated behavior.

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 coverage is 100% and the schema already documents `repo`, `repos`, and `project` including the batching behavior and fallback resolution. The description's note that passing `repos` yields 'one answer for all of them' merely restates the schema, so no meaningful value is added.

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 — generate the Carrick setup files — and enumerates exactly what gets produced (GitHub Actions workflow, Carrick skill, carrick.json, Claude Code hooks). This clearly separates it from the read/query siblings like get_project_map or list_services.

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?

It gives practical guidance to pass all repos in `repos` for a single answer, and describes the intended end-to-end flow (seed carrick.json from the `carrick init` proposal, end in first scan). However, it never states when NOT to use it or names any alternative among the siblings, so usage is only implied.

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