revit-mcp

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose whether this is a temporary visualization or permanent change, if it requires specific permissions, what happens on view changes, or any performance/rate limitations for large element sets.

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?

Two concise sentences that efficiently convey the core functionality. The first sentence states the action and key parameters, while the second explains the coloring logic. No wasted words or redundant 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 4-parameter visualization tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'coloring elements' means in practice (overrides? filters?), what the user sees as a result, or important constraints like which views support this operation.

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 100%, providing complete parameter documentation. The description adds minimal value beyond the schema, only implying that 'parameter value' drives color assignment without explaining how values map to colors or what happens with null/missing values.

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 the action ('color elements') and specifies the mechanism ('based on a category and parameter value'), distinguishing it from sibling tools like 'get_current_view_elements' or 'delete_element'. However, it doesn't explicitly differentiate from tools like 'operate_element' that might also affect element appearance.

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 alternatives. It doesn't mention prerequisites (e.g., needing an active view), exclusions, or comparisons to sibling tools like 'tag_all_walls' for visualization purposes.

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