Install Store Application

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

Discloses mutative, long-running, blocking nature and that installation adds tables/scripts/config. No annotations provided, so description carries burden well.

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?

Front-loaded purpose, then important notes and bullet points. Well-structured but slightly verbose; each sentence earns its place.

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?

Covers operation overview, prerequisites, related tools. No output schema, but description sufficiently prepares agent for a mutative 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?

Adds context beyond schema (e.g., linking get_app_details for app_id/version, search_store_apps for app_id). Schema coverage 100% means baseline is 3, but extra guidance raises it.

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?

Clearly states 'Install a ServiceNow store application' which is a specific verb and resource, and distinguishes from sibling tools like install_from_app_repo.

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?

Provides prerequisites (review app details, sufficient capacity, entitlements, test on sub-prod) and directs to use search_store_apps. Does not explicitly name alternatives or when not to use.

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