Capture a still to the vault gallery

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

Annotations indicate write (readOnlyHint=false) and non-destructive (destructiveHint=false) with openWorldHint=true. Description confirms it writes PNG images and appends to note, adding details on file structure and default behavior. 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?

Three sentences, no wasted words, front-loaded with main action and result. Clearly structured with purpose, mechanism, and usage.

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 all necessary aspects: what it does, where files go, default behavior, prerequisites. No output schema needed as actions are fully described.

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% but description adds meaning: explains note defaults to today's date for accumulation, gallery subfolder, and width/height defaults. Provides context beyond schema definitions.

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?

Description clearly states verb 'Captures', resource 'preview still from a TOP', and purpose: appends to a dated gallery note in Obsidian vault. Distinguishes from sibling tools like record_movie or snapshot_td_graph by specifying the exact action and target.

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?

Provides explicit use cases: 'Use this to document looks, reference frames, or build a browsable gallery of your session's visuals.' Also notes prerequisite: 'Requires a configured TDMCP_VAULT_PATH.' Does not explicitly exclude alternatives but gives sufficient context.

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