list_layouts

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the operation is a read-only listing and scopes it to the current project, but it does not mention return order, potential emptiness behavior, or any error conditions. The output schema may cover return structure, but some behavioral context is still missing.

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 concise sentence with no filler. It front-loads the main action ('List all layouts') and then specifies the scope and output content, making it easy for an agent to quickly 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?

For a zero-parameter read-only tool with an output schema, the description is largely complete: it names the resource, scope, and displayed properties. It could be more complete by adding a note about the current project context and perhaps clarifying that no changes are made, but the essential information for invocation is present.

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?

The tool has zero parameters, so the schema is trivially covered and there are no parameter semantics to document. The baseline of 4 applies, and the description accurately indicates what information will be returned for each listed layout.

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 verb ('List'), a specific resource ('all layouts'), and the scope ('in the current ArcGIS Pro project'), along with the information included ('page size and units'). This distinguishes it from sibling tools like create_layout and export_layout, which operate on layouts differently.

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 intended use is implicitly clear: call this when you need to enumerate layouts in the active project. However, there is no explicit guidance about when not to use it or any direct comparison to alternatives, though no sibling tool appears to be a competing list-layouts operation.

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