tag_walls

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

Describes behavioral details like centering tags, default tag type selection, and optionally showing leader lines. No annotations provided, but description provides sufficient transparency.

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?

Well-structured with core action first, followed by details and Args section. Slightly verbose with 'MCP context for logging' but overall efficient.

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?

Covers purpose, parameters, and behavior. Lacks explicit description of return value or output, but this is likely non-essential for a tagging tool. No output schema, so description need not explain returns.

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?

Adds meaning beyond schema: use_leader controls leader lines, tag_type_name specifies a specific tag family type. Schema coverage is 0%, but description fully explains both parameters.

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 uses specific verb 'tag' and resource 'untagged walls in current Revit view', clearly distinguishing from siblings like tag_elements which tag selected elements.

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?

Clearly states when to use (tag all untagged walls in current view), but does not explicitly mention alternatives or when not to use.

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