convex_hull

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

With no annotations, the description carries the burden of behavioral transparency, but it omits important details: no mention of accepted geometry formats (e.g., WKT, GeoJSON), behavior with invalid or empty geometries, output geometry type (likely polygon or multipolygon), or coordinate system handling.

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?

While the one-sentence description is brief, it is under-specified and lacks helpful structure. It does not earn its place by adding value beyond the name; it essentially repeats the tool name.

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 simplicity (one parameter, output schema exists), the description is incomplete. It should specify accepted geometry types, output type, and edge cases (e.g., empty input). The output schema may mitigate partial needs, but the description itself is insufficient.

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 has 0% description coverage for the 'geometry' parameter. The description does not clarify the expected format (e.g., WKT, GeoJSON, binary) or constraints (e.g., must be a polygon or linestring). This essential information is missing.

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 uses a clear verb 'Calculate' and a specific resource 'convex hull of a geometry', which distinguishes it from sibling tools like 'buffer', 'envelope', or 'simplify'. The purpose is unambiguous.

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 guidance is provided on when to use this tool versus alternatives like 'envelope', 'minimum_rotated_rectangle', or 'buffer'. There is no mention of prerequisites or typical use cases.

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