Create Table

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

The annotation readOnlyHint=false already signals mutation, so the description is not required to restate that. It adds minor behavioral context by revealing the two possible table representations (COM vs ezdxf composite), but it does not explain what 'explicitly-labelled' means or how the choice is made, and it says nothing about side effects or coordinate behavior.

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 a single sentence with no filler and gets straight to the point. However, the phrase 'explicitly-labelled ezdxf composite table' is dense and may require unpacking, so it is not perfectly clear despite being concise.

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?

While the schema covers parameter details and an output schema exists, the description fails to clarify the operational distinction between the two table types or when each is produced. For a 9-parameter creation tool, this missing behavioral context is a notable gap that an agent would need to resolve to use the tool fully correctly.

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 78% and every parameter has its own description, so the schema carries the parameter-level burden. The tool description adds no parameter-specific meaning beyond the schema, which is acceptable given the high coverage.

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 states a clear action ('Create') and a specific resource ('table'), distinguishing it from the many entity_create_* siblings like line, circle, and text. The clause about native COM vs ezdxf composite table adds specificity, though the jargon may be opaque to agents unfamiliar with the CAD library.

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?

There is no guidance on when to use this tool versus other entity creation tools, nor any mention of prerequisites or conditions determining whether to create a COM table versus an ezdxf composite table. The description leaves usage entirely to inference.

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