Update Store Application

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

The description adds substantial behavioral context beyond the annotations: it warns that the operation is MUTATIVE, LONG-RUNNING, blocks until completion or timeout (default 30 minutes), and may alter behavior, modify tables, affect customizations, and overwrite customizations. This goes well beyond the destructiveHint annotation and provides critical risk information.

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 and well-structured, with a brief opening, a bulleted list of warnings, and a practical usage tip. Every sentence earns its place, and the formatting improves readability without unnecessary fluff.

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 thoroughly covers the mutation risks, blocking behavior, timeout, and discovery method. It does not describe the return value format, and since there is no output schema, this is a minor gap. However, for a mutative tool, the focus on side effects and safety is more important, and the description handles that comprehensively.

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%, so the schema already documents all parameters. The description adds extra meaning by telling users to use search_store_apps to find the app_id and get_app_details for version, enriching the schema descriptions with practical sourcing guidance. Timeout default is also mentioned.

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 updates an installed ServiceNow store application to a newer version, using a specific verb and resource. It distinguishes from siblings like install_store_app (installing new apps) and search_store_apps (searching for updates), making the purpose unambiguous.

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 explicitly instructs to use search_store_apps with tab_context 'updates' to find apps with available updates, and advises testing on a sub-production instance first. It provides clear context for when to use this tool, though it does not explicitly state when not to use it or name alternative tools beyond search_store_apps.

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