service_area

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

With no annotations, the description fails to disclose critical behavioral traits such as overwrite behavior, what happens on failure, or the nature of the output. The requirement for Network Analyst is mentioned, but many other aspects are omitted.

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 a single, clear sentence that conveys the core purpose. It is concise but could be slightly improved by adding a second sentence for usage context.

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?

Despite having an output schema, the description does not mention what the output polygons contain (e.g., fields like ObjectID, shape, etc.). For a complex tool with many parameters and a nested input object, the description is insufficiently detailed.

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 input schema provides detailed descriptions for each parameter, so the description adds minimal value beyond stating 'Reachable-area polygons'. The parameter semantics are already clear from the schema, earning a 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?

Description clearly states the tool computes reachable-area polygons around facilities at travel cutoffs. It names the underlying function (MakeServiceAreaAnalysisLayer) and distinguishes from sibling tools like 'route_analysis' or 'closest_facility' by specifying polygon output.

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?

No explicit guidance on when to use this tool versus alternatives. The only context is 'Requires Network Analyst', which is a prerequisite. No mention of which scenario suits this tool best (e.g., for area-based analysis vs. point-to-point routes).

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