Install from App Repository

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

Despite no annotations, the description explicitly labels the operation as 'MUTATIVE, LONG-RUNNING' and states it blocks until completion or timeout (default 30 min). This discloses key behavioral traits beyond a simple verb, but could mention auth requirements or side effects.

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?

Two sentences: first sentence clearly states purpose and key behavioral traits; second provides usage guidance and a related tool. Every sentence is valuable with 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 complexity (7 parameters, long-running, no output schema), the description covers purpose, behavior, and usage guidance. It could be more complete by mentioning what the response contains (e.g., installation status or ID), but is sufficient for an install 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?

Schema coverage is 100% with detailed parameter descriptions. The tool description adds minimal parameter meaning beyond mentioning 'scope' and 'sys_id' as required and version defaulting to latest, which is already in 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 verb 'Install' and the resource 'application from the company's ServiceNow application repository'. It distinguishes from sibling tools like 'install_store_app' by specifying 'from the company's... repository' and mentions typical usage for deploying custom apps across instances.

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?

It provides context on when to use (deploying custom applications across instances) and suggests using 'list_company_apps' to find scope/sys_id. However, it does not explicitly contrast with 'install_store_app' or state when not to use, leaving some ambiguity.

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