add_layer_to_map

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: operates on saved .aprx files (not live sessions), saves when save=true, and uses arcpy.mp addDataFromPath. It does not mention error conditions or permissions, but the core safety profile (non-destructive addition) is evident.

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?

Three tightly written sentences deliver purpose, usage context, and behavioral note without extraneous words. Every sentence earns its place, making it efficient for an AI agent to parse.

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 presence of a comprehensive schema and an output schema (not shown), the description provides enough context: operation, data types, saved-file constraint, and save behavior. It could mention default map_name behavior or potential errors, but overall it is largely complete for a tool of this complexity.

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 descriptions cover all four parameters with sufficient detail, so the baseline is 3. The tool description does not add additional semantic information about parameters beyond what the schema already provides, meeting the minimum but not exceeding.

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 'Add', the resource 'dataset to a map inside an .aprx project', and provides examples of supported data types. It distinguishes from live sessions and mentions the underlying arcpy method, leaving no ambiguity about the tool's function.

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 gives context for when to use the tool ('before styling, exporting, or layout automation') and mentions it operates on saved files, implying it's for batch/automation workflows. It does not explicitly contrast with sibling tools like remove_layer_from_map, but the unique operation (adding) is clear.

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