Log a performance to the vault

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

Annotations indicate non-destructive (destructiveHint=false) and open world (openWorldHint=true). Description adds file naming details and optional thumbnail behavior, consistent with annotations. No contradictions.

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?

Description is two sentences plus file path detail, clear and front-loaded. Efficient but could be slightly more concise; no waste.

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 6 parameters, no output schema, and annotations, the description covers purpose, output location, and requirement. Lacks error handling or prerequisite details beyond vault path, but sufficient for basic usage.

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 covers 67% of parameters with descriptions; tool description only adds context about 'optional preview thumbnail' for output_path. No additional meaning beyond schema for other parameters, so baseline 3 is appropriate.

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 clearly states the tool logs a performance-journal entry with a network snapshot and optional thumbnail, written to a dated file. It distinguishes from siblings like snapshot_td_graph by emphasizing the journal aspect and specific file path.

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 implies usage for building a diary of shows and requires TDMCP_VAULT_PATH. It provides context but lacks explicit when-not-to-use or alternative comparisons, though the purpose is clear enough for an agent.

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