append_features

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

No annotations provided, so description carries full burden. It states the tool mutates the target dataset and requires confirm=true. It does not disclose failure behavior, authorization needs, or reversible nature. The mention of ArcPy Append adds technical context but is insufficient for full transparency.

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?

Three sentences, each serving a purpose: action, use cases, and constraint. No fluff, front-loaded with key information. Efficient and clear.

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?

Description covers purpose and mutation behavior but misses important context: prerequisite that target must exist, schema_type behavior details, error handling, and PathGuard restrictions mentioned only in schema. Output schema exists but is not described. Adequate but with noticeable gaps.

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 descriptions cover all four parameters (inputs, target, confirm, schema_type) with clear explanations. Baseline is 3 per rubric. The tool description adds only the confirm=true requirement, which is already stated in schema. No additional semantics provided.

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?

Description clearly states the tool appends rows to an existing target using ArcPy Append. It specifies the verb 'append' and the resource 'existing target dataset.' While it doesn't explicitly differentiate from siblings like merge_features or copy_features, the action is distinct enough to infer usage.

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?

Description provides explicit use cases: 'load reviewed data, merge field-compatible updates, or add processed batches.' It also notes the requirement for confirm=true. However, it does not state when not to use this tool or provide alternatives among many sibling tools.

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