draw_point

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions drawing at (x,y), omitting any details about layer behavior, units, coordinate system, or whether it creates a persistent entity. This is minimal and lacks transparency for a drawing operation.

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 very short and front-loaded, with no wasted words. However, it is under-specified, lacking necessary context about parameters and behavior. It earns a middle score because it is concise but incomplete.

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?

For a simple drawing tool with a small schema, the description still fails to address key context like the layer parameter, output/return behavior, or coordinate system. The sibling tools provide some context, but the description itself is too sparse to be complete.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It only mentions x and y, ignoring the layer parameter entirely, and does not explain coordinate units, origin, or default behavior. The description adds almost no semantic value beyond the parameter names.

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 'Point at (x,y).' clearly indicates the tool creates a point at specified coordinates. It uses a specific verb and resource, distinguishing it from sibling drawing tools like draw_line or draw_circle, though it could be more explicit about drawing a point entity.

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. The description only states what it does, with no context about coordinate systems, layers, or prerequisites, and no mention of when a point is preferred over other primitives.

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