build_fluent_app

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

The annotation idempotentHint=true already covers idempotency. The description adds behavioral context by stating 'Does NOT require instance authentication', which is valuable for an agent deciding to invoke without credentials. However, it doesn't disclose whether the build produces specific artifacts or modifies the source tree, so it's not a full behavioral disclosure.

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?

Three sentences, each earning its place: purpose, prerequisite, and explicit sequencing plus auth note. No wasted words, front-loaded with the primary action.

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?

The description is complete for a simple build tool: it covers what, when, prerequisites, and auth requirements. It doesn't explicitly mention the output artifact, but the phrase 'application package' implies the result. With only two optional params and no output schema, the description provides adequate context for an agent to invoke 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 coverage is 100% with both 'debug' and 'workingDirectory' having clear descriptions in the input schema. The description itself does not add parameter-specific meaning, but since the schema already fully documents them, the baseline is appropriate.

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 opens with 'Build a Fluent (ServiceNow SDK) application package from source code', which is a specific verb and resource combination. It also distinguishes itself from sibling tools by explicitly placing it 'after init_fluent_app and before deploy_fluent_app'.

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?

Explicitly states 'Run after init_fluent_app and before deploy_fluent_app', giving clear workflow sequencing. It also specifies the prerequisite 'valid Fluent project directory with now.config.json' and notes that instance authentication is not required, helping the agent decide when to use it.

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