download_fluent_app

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

The annotations already indicate destructiveHint: true and openWorldHint: true. The description adds context about expanding the application to a directory and including metadata not present locally, but it does not explicitly disclose potential overwriting of local files. It does mention authentication auto-injection, which is helpful.

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 concise, uses three sentences, and is front-loaded with the main purpose. Every sentence adds value: what it downloads, extra inclusion note, directory purpose, incremental mode, and authentication requirement. No wasted words.

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?

Given the tool's complexity (6 parameters, 100% schema coverage) and annotations, the description provides sufficient context for invocation. It covers the core purpose, directory semantics, incremental mode, and authentication. It does not elaborate on return values or failure modes, but no output schema exists and the tool seems straightforward for a download operation.

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 schema already covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds extra meaning to 'directory' by explaining it specifies where to expand the application, and to 'incremental' by explaining it downloads only changes since the last download, which goes beyond the schema.

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 downloads application metadata from a ServiceNow instance to a local directory, with a specific verb and resource. It does not explicitly distinguish itself from download_fluent_dependencies, but the phrase 'application metadata' implies a different scope from dependencies.

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 implies when to use the tool by describing its core purpose and mentions incremental mode, but it does not explicitly name alternatives or exclusion scenarios. There is no direct comparison with download_fluent_dependencies or other sibling tools.

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