cad_text_style

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

Annotations already indicate destructive behavior approximating, so the description does not need to restate that. The additional note about CJK text being assigned a Unicode-capable style is a useful behavioral detail. However, side effects of update or apply, such as modifying existing entities or changing current style state, are not disclosed.

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 compact and front-loaded with the main operations; the second sentence adds a genuinely useful behavioral detail. It is appropriately sized, though not formatted for easy parsing of the multiple action branches.

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?

This is a 13-parameter tool with a nested target objectadian destructive annotations and no output schema, yet the description does not explain target semantics, action-specific requirements, or parameter interactions. An agent cannot reliably construct a correct call for actions like apply or update from this description alone.

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 only 23%, and the description does not explain the many undocumented parameters such as target, name, fontFile, vertical, zoomToResult, or expectedRevision. The description adds no parameter-level meaning to compensate for the low schema 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 names specific operations (list, create, update, set current, apply) on AutoCAD text styles, which clearly identifies the resource and verb. However, 'apply' remains somewhat ambiguous without more context, and the description does not explicitly differentiate it from sibling 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?

The description provides no guidance about when to use this tool instead of siblings, no prerequisites, and no explanation of how the different actions relate to one another. The CJK note implies a particular use case but does not help an agent decide between actions or alternatives.

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