vba_custom_properties

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, but it only states 'generate VBA' without revealing side effects (e.g., whether it modifies any existing data, requires specific permissions, or has rate limits). The behavior beyond generation is opaque.

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?

At five words, the description is extremely short but not effectively concise—it sacrifices necessary detail for brevity. For a tool with 5 parameters (including nested objects and enums), the description should front-load key behavior rather than leaving all details to inference.

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's complexity (5 parameters, nested object, enums) and the absence of an output schema, the description is severely incomplete. It does not explain what the generated VBA does, how parameters interact, or what the agent can expect as a result of invoking the tool.

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?

The input schema has 0% description coverage for its parameters, and the description adds no meaning beyond the schema's property names and enums. The nested 'properties' array and fields like 'configuration' are completely unexplained, leaving the agent without guidance on how to populate them.

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 explicitly states the action ('Generate VBA') and the resource ('managing custom properties'), which clearly conveys the tool's purpose. It distinguishes itself from sibling VBA tools by focusing specifically on custom properties, but could be more specific about the output format.

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 on when to use this tool versus the many sibling VBA tools (e.g., vba_advanced_features, vba_batch_operations). It lacks any context about prerequisites, limitations, or complementary tools.

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