create_feature_class

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

With no annotations, the description carries full burden for behavioral traits. It mentions the default location and geometry type options but omits critical details like what happens if the name already exists, whether overwrite is allowed, required permissions, or side effects. This is insufficient for a 6-parameter creation tool.

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 very short (26 words), which is efficient but at the cost of missing necessary information. It is front-loaded with the key action and default, but lacks structure for parameter details or usage guidance. It could be slightly longer to include critical parameter hints without being verbose.

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 has 6 parameters, no output schema documentation, and no annotations, the description is severely incomplete. It covers only the geometry type and default location, leaving out behavior for name conflicts, coordinate system, map association, and output path. An output schema exists but is unhelpful without description.

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 coverage is 0%, so the description must explain parameters. It only provides semantics for geometry_type (listing valid values). Other parameters like epsg, map_name, out_path, and add_to_map are unexplained, leaving the agent to guess their meaning or format. This adds minimal value beyond the bare schema.

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 creates a new feature class, specifies the default location as the project's default geodatabase, and lists the valid geometry types (POINT, MULTIPOINT, POLYLINE, POLYGON). This is specific and distinguishes it from sibling tools like add_field or create_map, which have different purposes.

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 provides no guidance on when to use this tool versus alternatives, such as when to create a feature class vs. use run_geoprocessing_tool or add_layer. There are no explicit when-to-use or when-not-to-use conditions, leaving the agent without decision support.

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