fusion_sketch_rectangle

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

The description adds value beyond annotations by noting that the tool 'creates a new sketch on plane unless an existing sketch is given.' This discloses side effects and context. Annotations indicate readOnlyHint=false and openWorldHint=true, which are consistent.

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 extremely concise with two sentences, front-loading the action 'Draw a rectangle' and providing essential options. No extraneous 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?

For a simple shape-drawing tool, the description covers the key behavioral differences (mode, sketch vs plane) and units. No output schema exists, but the return value is implicit (the rectangle is drawn). Slight room for more detail on parameter formatting.

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?

With 0% schema description coverage, the description must compensate. It explains the meaning of x,y relative to mode, and mentions plane/sketch. However, width and height are only implied as dimensions in mm, not explicitly described. Some parameters (e.g., default values) are not detailed.

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 'Draw a rectangle' and specifies the resource (sketch) and units (mm). It explains the two modes ('corner' and 'center'), making the tool's purpose distinct from other sketch tools like circle or line.

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 explains when to use the tool (to draw a rectangle) and details the mode options. It does not explicitly state when not to use or provide alternatives, but the context is sufficient for selection among sibling tools.

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