Turf-MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an excellent job describing what the tool does, including input requirements (JSON strings, specific GeoJSON formats, grid arrangement constraints), output format (GeoJSON FeatureCollection with LineString features), dependencies (Turf.js, Node.js), and error conditions (JavaScript execution failures, timeouts, data format errors). The only minor gap is it doesn't mention performance characteristics or rate limits.

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 well-structured with clear sections (Args, Returns, Raises, Example, Notes) and front-loads the core purpose. While comprehensive, it's appropriately sized for a complex tool with 3 parameters and no annotations. Every section adds value, though some redundancy exists between the Args section and the Notes section regarding JSON string requirements.

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's complexity (3 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description is remarkably complete. It covers purpose, parameters, return values, error conditions, examples, and important constraints. The output schema existence means the description doesn't need to exhaustively document return values, and it provides exactly the right level of contextual information for effective tool use.

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?

With 0% schema description coverage, the description fully compensates by providing comprehensive parameter documentation. Each parameter (point_grid, breaks, options) gets detailed explanations including types, formats, examples, and optional fields. The description adds significant value beyond the bare schema, explaining JSON string requirements, GeoJSON structure, coordinate systems, and configuration options.

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's purpose with a specific verb ('生成等值线' - generate isolines) and resource ('从点网格' - from a point grid). It distinguishes itself from sibling tools like 'interpolation_interpolate' or 'interpolation_isobands' by focusing specifically on creating line representations of continuous values from point grids, not other interpolation methods.

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 implies when to use this tool (for creating continuous value line representations from point grids) but doesn't explicitly state when NOT to use it or name alternatives. It mentions the tool is for '等值线用于可视化连续数据的等值边界' (isolines for visualizing continuous data boundaries), which provides some context, but lacks explicit comparison with other interpolation tools in the sibling list.

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