multipart_to_singlepart

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

With no annotations provided, the description carries full responsibility. It discloses that the tool reads in_features and creates out_features without modifying the source dataset, which is good. However, it does not mention error conditions (e.g., what happens if input is already singlepart), performance implications, or permission requirements. More behavioral context would elevate this score.

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 two sentences: the first states the action and method, the second provides usage guidance. It is concise, front-loaded with the essential verb and resource, and contains no extraneous information. Every sentence earns its place.

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 that the tool has an output schema (not shown but present) and no annotations, the description covers the core purpose, usage context, and non-destructive behavior. It lacks details about output format or side effects, but for a simple split operation with an output schema, it is sufficiently complete. A small gap is the absence of edge cases.

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 schema descriptions for parameters are comprehensive and cover the meaning of in_features, out_features, and overwrite. The description adds only 'Reads in_features and creates out_features,' which adds minimal value beyond what the schema already provides. Since the schema already does the heavy lifting, a score of 3 is appropriate.

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 uses ArcPy MultipartToSinglepart to split multipart features into singlepart features, which distinguishes it from sibling tools that perform other operations (e.g., dissolve, merge). It identifies the resource (features) and the action (split).

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 states when to use the tool: 'before per-feature editing, counting, topology checks, joins, or analysis that requires one geometry part per row.' It does not explicitly list when not to use it, but the use cases imply that it is inappropriate when multipart geometry is needed. A clear exclusion or alternative would improve the score.

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