rush_ci

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

With no annotations supplied, the description carries the behavioral disclosure burden. It does so well by stating the operation is inspection-only and explicitly ruling out credential and remote-status access. It doesn't enumerate failure modes or whether the config is merely read, but 'inspect' plus the exclusions provide a clear non-mutating profile.

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?

A single tightly packed sentence that front-loads the purpose and then adds the key constraints. There is no filler or repetition.

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?

This is a simple one-parameter read-oriented tool and an output schema is present, so the description doesn't need to explain return values. It covers the main safety-relevant behavior (no credentials/remote status). The only slight gap is not clarifying path semantics, but the overall context is strong.

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 only parameter, 'path', has no schema description (0% coverage), so the prose must compensate for parameter meaning. The description's 'local CI workflow configuration' makes it inferable that the path points to a CI workflow configuration, but it never explicitly states whether the path should be a file or directory, or how it relates to the CI config. This is adequate but not fully explicit.

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 uses a specific verb ('Inspect'), names the resource ('local CI workflow configuration'), and adds two explicit exclusions ('without accessing credentials or remote status'). This clearly differentiates it from remote/credential-related siblings and is far beyond a restatement of the name.

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 clearly implies when to use: when you need to inspect local CI workflow configuration and do not need remote status or credentials. However, it does not name any alternative tools or state explicit when-not conditions in relation to siblings, so it stops short of a 5.

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