extract_sketch_to_gis

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

Since no annotations are provided, the description bears full responsibility for behavioral disclosure. It explicitly states that the tool appends data (non-destructive) and requires confirm=true. The pipeline steps provide context on what happens internally. However, it lacks information on error handling or success/failure conditions.

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 exceptionally concise: three sentences plus a note, no redundant information. It front-loads the core pipeline and critical constraint (confirm=true). 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?

For a complex pipeline tool, the description outlines the main steps and important constraints (confirm, environment). However, it omits details like coordinate system handling, failure behavior, and the required format of the base_layout. Given the presence of an output schema (which may cover return values), the description is moderately complete.

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 description does not elaborate on individual parameters; all parameter semantics are handled by the input schema, which has high coverage (each parameter has a description). Thus, the description adds no extra meaning beyond the schema, earning the baseline score of 3.

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 provides a clear and specific verb-resource pair: 'extract sketch to GIS'. It outlines a multi-step pipeline (alignment, extraction, georeferencing, appending) that distinguishes it from all sibling tools, none of which handle sketch-to-GIS workflows.

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 states that the tool 'APPENDS rows — requires confirm=true', giving a clear condition for use. It also mentions environment dependencies. However, it does not provide guidance on when to avoid this tool or suggest alternatives, which would improve decision-making.

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