Simplify Geometry

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by naming the Douglas-Peucker algorithm and stating offline capability, which are not in annotations. No contradictions.

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?

Description is four concise sentences with no redundancies. Each sentence adds information: operation, algorithm, use case, and offline capability.

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?

With an output schema present, description does not need to explain return values. It covers algorithm, use cases, and offline behavior. Minor gap: no mention of coordinate system, but this is standard for such tools.

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 100%, so baseline is 3. Description does not add parameter-specific details beyond the schema, but it contextualizes the tolerance parameter by mentioning the algorithm.

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 it simplifies LineString or Polygon by reducing vertices while preserving shape, using the Douglas-Peucker algorithm. It distinguishes from siblings like area, centroid, and buffer tools, which perform different operations.

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 mentions usefulness for reducing file sizes and improving rendering performance, and that it works offline. While it does not explicitly exclude cases, the context is clear and implies appropriate use cases.

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