get_extent

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

No annotations provided, so the description carries full burden. It states the tool reads metadata only, does not modify the dataset, and uses a specific ArcPy method. It does not detail error handling or performance, but for a simple read operation, this is sufficient.

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 three sentences long, no extraneous text. It front-loads the core purpose, then gives usage guidance, and ends with a safety note. Every sentence adds value.

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 tool's simplicity (one parameter, no nested objects), and the presence of an output schema, the description is nearly complete. It specifies the return values and use cases. Minor gaps: no mention of validation behavior or error cases, but adequate for most scenarios.

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% per context, meaning the tool description must compensate for parameter details. However, the description does not add any information about the 'dataset' parameter beyond what the schema already provides. The schema itself has a detailed description, but the tool description adds no additional value for parameter 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 clearly states the tool returns xmin, ymin, xmax, ymax, and CRS metadata using ArcPy Describe().extent, which distinguishes it from sibling tools like describe_dataset. It specifies exact outputs and the method used.

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 explicitly lists use cases: before clipping, map export, fishnet creation, raster analysis, or spatial QA/QC. It also notes that it reads metadata only and does not modify data, implying safety. However, it does not explicitly mention alternatives or when not to use it.

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