Import Document

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

Annotations provide readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, which already tell the agent this is a local, non-destructive, non-idempotent write operation. The description adds only that the import is restricted to a controlled input root and that it returns a list of added items. It doesn't disclose side effects like what happens on name collisions, whether the project is saved automatically, or permission requirements. With annotations covering the safety profile, this is a moderate addition.

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 a single, efficient sentence that front-loads the action and scope. It contains no filler or repetition. It could be expanded slightly to cover when-to-use, but as written it is appropriately concise for its information content.

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 tool has 5 parameters, no schema descriptions, and no output schema description (although has_output_schema=true, so the return format is implied). With zero parameter documentation in the schema, the description should explain the parameters and the import behavior in more detail. As it stands, an agent knows only the file types and the return summary, leaving key operational details (what each flag does, whether the project must be open, where the 'controlled input root' is) unspecified. This is a significant gap.

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% and there are 5 parameters, so the description must compensate, but it only conveys that a document path is expected and hints at a controlled input root. It doesn't explain aprx_path, log_files, include_layout, or reuse_existing_maps. The single sentence about the import scope is the only parameter guidance. This is thin but not absent; a 3 reflects that the schema itself provides the parameter list, yet the description fails to enrich the semantics.

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 states a specific verb (导入/import) and resource (MXD/3DD/SXD/MAPX/PAGX/RPTX documents into a project), and it names the output behavior (returning a list of newly added items). The sibling set contains many import-like tools (import_bookmarks, import_attribute_rules) but this one is distinguished by its document-type scope. However, it does not explicitly differentiate from the closest sibling, arcgis_pro_gp_import_csv_to_table etc., whose names suggest they import different formats. Still, the purpose is 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 implies the tool's purpose (import a document) but offers no when-to-use guidance, no prerequisites, and no mention of alternatives. Given the large sibling set, an agent has no explicit signal about when to pick this over importing via other means. Usage is inferable from the name but not stated.

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