revit_capture_screenshot

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

No annotations are provided, so the description carries the full burden. It implies a side-effecting capture against the currently active view but says nothing about permissions, latency, whether it overwrites a previous capture that revit_get_latest_screenshot would return, or any failure/threading behavior.

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?

A single, front-loaded sentence with no padding or redundancy. It is efficient but borders on under-specification given the tool's behavioral opacity.

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?

The output schema covers return values, and the capture target is stated. However, with no annotations, an unexplained port/doc_name pair, and no relation to the sibling screenshot tool, the definition leaves an agent guessing at how to invoke it correctly.

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 0% and neither 'port' nor 'doc_name' is mentioned in the description. The phrase "currently active view" implies no view-selection parameter, but the two actual parameters remain entirely unexplained, so the description does not compensate for the schema gap.

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 states a specific verb pair ("triggers and captures") and resource ("high-resolution screenshot of the currently active view in Revit"), so the agent can tell what it produces. It does not explicitly name or distinguish itself from the near-identical sibling revit_get_latest_screenshot, leaving the capture-vs-retrieve distinction to inference.

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?

There is no explicit when-to-use guidance, no exclusions, and no reference to alternatives. The existence of a sibling revit_get_latest_screenshot makes the missing routing rule (capture now vs. fetch the last capture) a real gap.

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