Import repository

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true. The description adds real value beyond that by disclosing the raised exceptions (MissingParameterError when repo_url is absent, ParameterError for a non-boolean auto_upgrade_base_app) and the return type. It still omits auth/permission requirements and any side effects of the import.

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 docstring-style structure with param/return/raises sections is easy to scan and front-loaded with the verb. However, the opening sentence carries filler and the bulk is a partial param list rather than prioritized guidance.

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?

For a 43-parameter tool with no output schema and zero schema description coverage, the definition is markedly incomplete. Most parameters are undocumented and there is no guidance on how parameters interact or which combinations are valid.

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 description coverage is 0% across 43 parameters, so the description must carry the burden. It documents only five (credential_sys_id, mid_server_sys_id, repo_url, branch_name, auto_upgrade_base_app), leaving roughly 38 parameters — including result_id, scan_type, update_set_*, and the various _sys_id fields — completely undescribed.

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?

States a clear verb+resource ('Import a repository'), but the phrase 'based on the provided parameters' is filler. It gives no differentiation from siblings such as servicenow_app_repo_install, servicenow_app_repo_publish, or servicenow_apply_remote_source_control_changes, so an agent cannot route among them from this text.

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?

There is no statement of when to use this tool, when not to, or which alternative to prefer. The only conditional guidance is buried in the error clauses, which describe failure modes rather than usage context.

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