list_mxd_layers

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal one important behavior: access is restricted to 'allowed roots'. However, it does not define those roots, explain what happens for invalid paths, or explicitly confirm whether the operation is read-only beyond the verb 'List'.

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 sentence that front-loads the verb and object. There is no repetition or filler; every phrase contributes either the action, the resource, or a restricting condition.

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 simple one-parameter shape and the presence of an output schema, the description is minimally adequate: it states the operation and the key constraint. It leaves gaps around the meaning of 'allowed roots' and when to prefer sibling tools, but these are not fatal for such a small, read-oriented tool.

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 the schema only labels mxd_path as a string. The description adds that the path should point to an MXD file within allowed roots, which is meaningful, but it does not specify path format, how allowed roots are determined, or expected path scope. It only partially compensates for the missing schema documentation.

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 a specific action ('List') and resource ('data frames and layers in an MXD file'), and it adds a useful scoping constraint ('within allowed roots'). It is distinct from generic purposes, though it does not explicitly contrast with the sibling describe_mxd or list_fields tools.

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 guidance about when to use this tool versus alternatives such as describe_mxd or query_features. The description only announces the operation and provides no scenario, prerequisite, or exclusion cues to help an agent select it correctly.

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