spatial_join

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

Describes core behavior (returns properties of containing polygon) and efficiency, but omits details on output format, handling of points outside polygons, or error conditions. With no annotations, the description carries full burden but doesn't cover edge cases.

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?

Three concise sentences: purpose comparison to sibling prerequisite. No wasted words, front-loaded with key information.

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?

Covers main usage and prerequisite, but lacks output details and error cases. Given no output schema, description could be slightly more complete, but is adequate for typical 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?

Schema coverage is 100%, so parameters are well-documented. Description adds value by reiterating prerequisite (dataset id from list_datasets) and coordinate requirement, but does not significantly expand beyond the schema.

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?

Clearly states it enriches coordinates with polygon attributes and compares to sibling check_location, making the purpose and distinction obvious.

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?

Provides clear prerequisite (call list_datasets first) and notes coordinate requirements. Implicitly suggests when to use this over check_location (multiple points), but lacks explicit when-not-to-use guidance.

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