tool_image_coordinates

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

With no annotations, the description carries full burden, but it offers no behavioral details—no indication of side effects, return semantics, permissions, or error behaviors. It merely restates schema fields.

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 text is concise and includes a clear list of parameters and outputs, but it is under-specified and uses a terse format that prioritizes brevity over usefulness.

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 no output schema and no annotations, the description should explain the operation and response. It does not, leaving the tool's functionality opaque even for basic usage.

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?

Though schema coverage is 100%, the parameter descriptions are trivial labels ('X', 'Y', 'File'). The description adds no explanation of what x/y represent (e.g., pixel coordinates, image-space) or the output structures. It fails to compensate for the shallow schema descriptions.

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 only states 'Image Coordinates' and lists parameters/outputs without specifying any action. It fails to convey what the tool does (e.g., compute, map, extract) and does not distinguish from sibling image 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?

No guidance on when to use this tool or when to prefer alternatives. The description lacks any contextual or conditional instructions.

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