vba_pattern_features

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

With no annotations, the description must fully convey behavioral traits, but it merely states a generic action. There is no information about side effects, required selection, output format (e.g., clipboard, file), or any constraints.

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 short (4 words), which may seem concise but lacks substance. It does not structure information effectively; it is a bare minimum phrase without any clarification of the tool's scope.

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 the tool has 7 parameters, nested objects, and no output schema, the description is completely inadequate. It fails to explain what 'pattern features' are, what the generated VBA does, or how parameters relate to the output.

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 57%, but the description adds no additional meaning beyond what the schema provides. For example, the schema describes 'axis' and 'angle' for circular patterns, but the description does not clarify when or how they are used.

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 'Generate VBA for pattern features' clearly states the tool's action (generate) and resource (VBA for pattern features). It distinguishes from sibling VBA generation tools that target different aspects, like vba_advanced_features or vba_batch_operations.

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 like vba_advanced_features or vba_create_reference_geometry. There are no explicit when-to-use or when-not-to-use statements.

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