td_screenshot

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

With no annotations, the description carries the full burden. It discloses the default output directory and the side effect of saving a file. However, it omits details like whether the file is overwritten, how the filename is generated, or any requirements (e.g., the TOP must exist). This is adequate for a simple save operation but not rich.

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 a single, compact sentence that leads with the action and includes the essential detail about the default location. Every word earns its place, and there is no redundant or filler content.

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 tool is simple, and the output schema exists so return values need no explanation. However, the description lacks critical context about the required top_path parameter and any prerequites. It gives purpose and a default, but a user might not know what to pass for top_path beyond the schema.

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 description coverage is 0%, so the description must compensate. It only hints at the 'file' parameter via 'default under td-mcp/shots', implying this can be overridden, but it completely ignores the required 'top_path' parameter. The description adds some meaning about the default output path but fails to explain the primary argument.

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 specific action ('Save a TOP's image to PNG'), the resource (a TOP), and the output format (PNG). It also mentions the default save location, distinguishing this from sibling tools like td_save which likely saves node configurations rather than visual snapshots.

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 'so the client can view it' provides clear context for when this tool is appropriate—when a visual representation of a TOP is needed. It doesn't explicitly exclude other tools or name alternatives, but the purpose is concrete enough to guide usage.

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