network_service_area

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

With no annotations, the description carries the full burden. It discloses key behaviors: the results are added as a new line layer, only a summary is returned, and the cost interpretation depends on strategy. However, it lacks information on error conditions, permissions, or performance implications.

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 concise, with two short paragraphs. It front-loads the purpose, and every sentence adds value (e.g., explaining cost units and side effects). No redundant or vague statements.

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 complexity (8 parameters, no schema descriptions) and an output schema for return values, the description covers main output and side effects but omits parameter details and usage scenarios. It is adequate but not complete for effective tool invocation.

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 0%, so the description must compensate. It explains the 'cost' parameter's unit based on strategy and indirectly references 'speed_field'/'default_speed'. But 5 of 8 parameters (tolerance, start_point, direction_field, network_layer_id, strategy default) receive no explanation, leaving significant gaps.

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 computes 'the reachable network area from a point within a travel-cost budget,' using a specific verb ('compute') and resource ('reachable network area'). It distinguishes itself from the sibling `network_shortest_path_layer` by referencing it, implying a different output type (area vs. path).

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 explains the cost units based on strategy and references `network_shortest_path_layer` for requirements, but it does not explicitly state when to use this tool versus alternatives like shortest path or other network tools. The use case is implied but not contrasted.

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