revit_get_latest_screenshot

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

No annotations are provided, so the description carries the full disclosure burden. It discloses the return content (metadata plus file path) and is implicitly read-only via 'Retrieves', but says nothing about behavior when no screenshot exists, error cases, or whether it reads from disk vs. app state.

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 tight sentence with the outcome and returned data front-loaded and no redundant phrasing.

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 zero-parameter getter with an output schema that documents the return shape, the description covers purpose and payload adequately. It could add a note on the empty/no-screenshot case, but nothing critical is missing for correct invocation.

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?

Zero parameters, so there is nothing for the description to clarify beyond the schema; the baseline of 4 applies. The description correctly indicates the tool takes no input.

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?

States a specific verb ('Retrieves') and resource ('most recently captured screenshot or user snip') plus the returned payload (metadata and file path). It distinguishes itself from capture-oriented siblings by emphasizing retrieval of the latest existing artifact rather than creating one, though it does not name any sibling explicitly.

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 phrase 'most recently captured' implies this is the post-capture fetch step, giving implied usage context, but the description never states when to prefer this over revit_capture_screenshot or revit_request_user_snip, nor any preconditions (e.g., requires a prior capture).

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