fluent_cicd

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

The description directly contradicts the annotations: it says WRITE_ENABLED=true and drives install/publish/testsuite actions, which are write operations, while annotations declare readOnlyHint=true. This is a serious safety inconsistency. Additionally, the description does not disclose side effects (e.g., publishing to app repo, installing app version, running tests) beyond the flags, so the agent cannot anticipate the mutation.

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 two sentences, front-loaded with the main purpose and immediately followed by the required flags. Every sentence adds value: the first states what it does and via what SDK, the second adds pipeline context and critical prerequisites. No filler or redundant repetition of schema fields.

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?

Despite good schema coverage, the tool performs mutating actions (install/publish/testsuite) and has no output schema, yet the description does not explain what happens on success, whether operations are synchronous, or how results are returned. The readOnlyHint contradiction further undermines completeness, leaving a critical gap for a CI/CD tool that alters instance state.

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 input schema has 100% coverage with clear descriptions for all 5 parameters, so the baseline is 3. The description adds no parameter-level detail beyond the schema, but it does mention the actions (install/publish/testsuite) that map to the action enum. No compensation is needed since schema fully documents each parameter.

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 clearly states the tool runs ServiceNow CI/CD operations via the SDK, specifically scoped-app install/publish and ATF test-suite runs. It uses specific verbs ('Run', 'Drive') and a distinct resource ('now-sdk cicd'), while also distinguishing itself from local build/install flows, which separates it from sibling tools like fluent_build and fluent_validate.

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 clear usage context: 'from a promotion pipeline, outside the local build/install flow' and lists required flags (FLUENT_ENABLED=true, WRITE_ENABLED=true). It implies when to use it but does not explicitly name alternative tools or state when not to use it, so it falls short of full exclusion guidance.

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