bdesign_editor_snapshot

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

The annotation readOnlyHint: true is consistent with the description's claim of 'inspection' and 'not a pixel screenshot,' which implies non-destructive behavior. However, the description does not disclose what data is returned or whether any state changes occur beyond the read-only implication.

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?

The description is brief but poorly structured. The first sentence is grammatically ambiguous and unclear, while the second provides a useful clarification but does not compensate for the vagueness.

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 lack of an output schema and unclear action, the description omits critical context about what a 'snapshot' entails, what 'resolve timeline clips' means, and what the tool returns. It is incomplete for an agent to reliably invoke it.

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 schema has two parameters (time and projectId) with no descriptions, and the description does not explain their purpose or relationship to the tool's action. Schema coverage is 0%, and the description fails to compensate.

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 it performs 'semantic inspection' and is not a pixel screenshot, but the phrase 'Resolve the active timeline clips at a time' is ambiguous and does not clearly define the tool's action or output. It fails to distinguish from sibling tools like bdesign_editor_view or bdesign_canvas_get.

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 indication of when to use this tool versus alternatives. No sibling tools are mentioned, and no use-case guidance is provided.

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