tabulate_intersection

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

No annotations provided, so description carries full burden. It mentions writing a standalone output table and using ArcPy, but fails to disclose key behavioral traits like required permissions, overwrite behavior, or side effects beyond the inherent schema.

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 two sentences, front-loaded with action and resource, followed by use case examples. It is concise without sacrificing clarity, though minor trimming is possible.

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 rich schema and no output schema, the description covers the tool's core purpose but lacks details on prerequisites (e.g., projection requirements) and output table structure, leaving some gaps for complex scenarios.

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 schema already describes each parameter in detail (e.g., out_table, zone_fields). The description does not add additional meaning beyond the schema, so baseline score is appropriate.

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 it cross-tabulates intersections between zone and class features using ArcPy TabulateIntersection, with concrete examples. It distinguishes from siblings by mentioning the specific tool and output table, but could explicitly differentiate from similar spatial analysis tools.

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 provides usage scenarios like quantifying land-use area by district or habitat type by planning unit, implying when to use. However, it lacks explicit guidance on when not to use or alternatives, leaving the agent to infer appropriateness.

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