Capture a still to the vault gallery

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

The description adds behavioral details beyond the annotations: it writes PNG images under a specific path and appends to a markdown note, defaulting to today's date. Annotations indicate a non-destructive write operation, which the description aligns with. No contradiction.

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 well-structured and front-loaded with the main action. It is slightly verbose but each sentence serves a purpose. Could be slightly trimmed, but overall effective.

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 description fully explains the tool's behavior, including the file operations and default behavior. Given the absence of an output schema, it adequately covers what the agent can expect. No gaps.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that 'note' defaults to today's date, and it describes the overall file structure (<gallery>/images/ and <gallery>/<note>.md). This provides context beyond the schema's individual parameter descriptions.

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 a specific verb ('captures') and resource ('preview still from a TOP') and clearly explains the outcome: appending to a dated gallery note in the Obsidian vault. It distinguishes from sibling tools by emphasizing the vault gallery and look-book building use case.

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 explicitly states when to use this tool: 'to document looks, reference frames, or build a browsable gallery of your session's visuals.' It also mentions a prerequisite (configured TDMCP_VAULT_PATH). However, it does not explicitly exclude scenarios where this tool should not be used.

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